Forum Discussion
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="******"
Content-Length: 71
Set-Cookie: NS_ROUTING_VERSION=LAGGING; path=/
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Keep-Alive: timeout=10, max=998
Connection: Keep-Alive
error code: INVALID_LOGIN_ATTEMPT
error message: Invalid login attempt.
- sonya_m4 years agoSmartBear Alumni (Retired)
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!
Related Content
- 4 years agoyassir
- 3 years agoalexandrebodart
- 3 years agoaaronpliu
Recent Discussions
- 23 hours agoarmygrad