Forum Discussion
Hi richie,
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.
Regards,
Jagruuti
Offend me? Youll have to try a lot harder than that fella.....in fact, most people that know me would say im pretty much unoffendable!
I appreciate that you want the tool to be able to exercise your requirements but if youre not using the tool in the method the RFCs and other supporting sources proscribe (when the tool has been coded to comply with those RFCs) then you can hardly blame the tool!
The fact that youre developers have just given you strings to input to help you out, just doesnt work in this situation. The OAuth functionality is configured for your to obtain those values yourself...which is how id suggest most people would need the functionality to behave.
I should highlight that you can still exercise apis using OAuth without using the OAuth functionality cos ive had to do this before myself (similar situation to you....my project didnt provide me with what i needed) so i setup the individual REST calls of the back and forth processing of the OAuth myself.
Just to be clear. Im not a Smartbear employee!
Nice one,
Rich