BUG: ReadyAPI is not calculating OAuth1.0 signature correctly if I use Content-Type as FORM

Question

ReadyAPI is not calculating OAuth1.0 signature correctly if I use Content-Type as application/x-www-form-urlencoded (FORM data).

It calculates and works fine if I use the Content-Type as application/json

I don't know what is the difference if anyone has seen this before. is there any workaround for the issue.

nastya_khovrina · Answer

Hi,
&nbsp;
I'm not aware of any known issue with this, so, please open a new case here:&nbsp;https://support.smartbear.com/message/?prod=ReadyAPI&nbsp;regarding the issue.

Forum Discussion

BUG: ReadyAPI is not calculating OAuth1.0 signature correctly if I use Content-Type as FORM

Related Content

Swagger Compliance Assertion: Invalid content type [image/bmp]

DELETE Method Without Content-Type Header?

ERROR:groovy.lang.MissingMethodException: No signature of method

Save API Response as Excel for Content-Type: application/ms-excel

Update Content-Type in Attachment before submission

Recent Discussions

Not able to Load data from Excel java.lang.NoClassDefFoundError

ReadyAPI Installation Keeps Failing on Intel Evo i7 – Need Advice!

ReadyAPI Error: Could not import a definition from the specified file.

Unable to open an Excel Data Source since file is Protected from Editing (Protected View)

In ReadyAPI, can you create Custom Test Step Properties for REST Request Steps?