ReadyAPI v1.9.0 authorization set in API definition no longer used - worked fine in v1.5.0

Question

In ReadyAPI v1.9.0, the auth settings for an endpoint no longer cause the Authorization header to be included in a REST test step. I have user and password setup in the API definition (on the Projects tab) instead of adding it to each request in every test case.

This is working fine in ReadyAPI v1.5.0 but not at all in v1.9.0.

Anything I can do to fix, except write a script to change every request step in my project?

nastya_khovrina · Answer

Hi Lars,
&nbsp;
Thank you for your post. Please try to reset the authentication profile for a service in the Auth Manager on the Projects tab. But note, that rules specified on lower levels have a priority over rules specified on higher levels. See the correspoding article:&nbsp;https://support.smartbear.com/readyapi/docs/projects/requests/auth/profile/inherit.html
BTW, did you reload the project?
&nbsp;
The latest version of ReadyAPI is 2.2.0, you can download it from here:&nbsp;https://support.smartbear.com/downloads/readyapi/

Forum Discussion

ReadyAPI v1.9.0 authorization set in API definition no longer used - worked fine in v1.5.0

1 Reply

Related Content

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

ReadyAPI: Using automated Authorization from Auth Repository

ReadyAPI and TestEngine with Zephyr Scale

ReadyAPI and TestEngine with Zephyr Scale

Invalid API Definition

Recent Discussions

How to hit update service multiple time with different data set.

How do I prevent a file path from being altered when being parsed by JsonSlurper in Groovy Script?

Darshan Hiranandani : Exploring ReadyAPI Integration with Azure Git

Multipart requests getting blocked by the Azure WAF 200003

Parameterising JDBC Connection Settings..Can you do it?