Hi, So the implementation is like we have oauth 1.0 in our API.
Signature method - HMAC-SHA256. Consumer key. Consumer secret. Access token. In header we have 3 keys, content type and other 2 keys. I have used oauth sampler ( though it's deprecated, I didn't find any other option). But unfortunately no success yet. Please let me know if you any further details. On Mon, 3 Feb 2020, 7:57 pm [email protected], <[email protected]> wrote: > The instructions will differ depending on the signature algorithm > (PLAINTEXT, > HMAC-SHA1, RSA-SHA1) so not knowing the details of your identity provider > it > is not possible to come up with the comprehensive solution. > > The algorithm of signature generation is described i.e. at Creating a > signature > < > https://developer.twitter.com/en/docs/basics/authentication/oauth-1-0a/creating-a-signature> > > article of Twitter developer API documentation. > > You may also find How to Run Performance Tests on OAuth Secured Apps with > JMeter > < > https://www.blazemeter.com/blog/how-run-performance-tests-oauth-secured-apps-jmeter/> > > article useful. > > > > -- > Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
