How to update HMAC-SHA1 to HMAC-SHA256 in android lib

[yokikathir]

HMAC-SHA1 will no longer be accepted as a signature method for TBA integrations. Before your account is upgraded to 2023.1, you must update your TBA integrations to use the HMAC-SHA256 signature method. Please solve the issue

[pakerfeldt]

Feel free to send a PR. I'm not actively working on this project anymore.

[levimllr]

signpost-core has a HmacSha256MessageSigner, and any extension of the AbstractOAuthConsumer (such as OkHttpOAuthConsumer) can set its message signer. Thanks to this, you can use the HMAC-SHA256 signature method in your consumer simply by adding a dependency on the latest version of signpost-core and doing the following:

    OkHttpOAuthConsumer consumer = new OkHttpOAuthConsumer(consumerKey, consumerSecret);
    consumer.setMessageSigner(new HmacSha256MessageSigner());

Would be nice to initialize the consumer with the appropriate signer, but that may be something to bring up with the signpost folks.