Unable to generate the access tokens for OAuth 1.0 as ReadyAPI/SOAPUI does not have few fields which accept string values. Example: As shown in the attached word document file.
Postman has fields which accept the values in string format whereas SOAPUI requires URL in some fields which restricts the user to perform API requests having OAuth 1.0 auth profile.
Thanks and Regards,
I'm sorry if I have offended here anyone by comparing Postman with ReadyAPI.
I have been initially using ReadyAPI in my project, but when I found that I was unable to create tokens for OAuth 1.0, I had to move to Postman.
I also tried importing the request from Postman for OAuth 1.0, the request was not working. So I'm using 2 tools in my project- Ready API for OAuth 2.0 and Postman for OAuth 1.0.
I'm trying to automate everything in one tool. So I want this feature to be there in ReadyAPI.
Also, I would read the back and forth functionality why only URLs are required.
But if my project comes up with this kind of requirements, then I think whichever tool I'm using should support all the requirements.
This is the basic expectation that I have. After all, I have bought the license for it.
Can you explain to me how I can exercise the API's having OAuth 1.0 without using the OAuth functionality of ReadyAPI?
And how do you set up the individual REST Calls of the back and forth processing of the OAuth?
Thanks and Regards,
Thank for providing the in-depth explanation Richie.
Hi @Jagruuti ! Please let us know if the reply was helpful!
Yes, DEV team has provided me with the hardcoded values.
So I directly used the Authorization value from the Postman in the header of the HTTP request in ReadyAPI.
I'm getting the below error, if I'm trying to follow the above method.
HTTP/1.1 403 Forbidden
Date: Tue, 18 Aug 2020 05:37:39 GMT
WWW-Authenticate: OAuth realm="******"
Set-Cookie: NS_ROUTING_VERSION=LAGGING; path=/
P3P: CP="CAO PSAa OUR BUS PUR"
Keep-Alive: timeout=10, max=998
error code: INVALID_LOGIN_ATTEMPT
error message: Invalid login attempt.
I apologize for the long wait. I see that you are investigating this with the support team (case 00447593). Please keep working with them, and we'll be happy to learn what solution they have to provide!