Forum Discussion

srixon's avatar
srixon
Occasional Contributor
3 years ago

How to handle when there is a separate Basic Auth endpoint and api endpoint for each environment

How to handle when there is a separate Basic Auth endpoint that returns a JWT and api endpoint for each environment   Here is the use case: 1.  There are multiple environments and each environment...
Automation Environments
Configuration
Test Setup
  • KarelHusa's avatar
    KarelHusa
    3 years ago

    srixon ,

    given the details you gave us above I would suggest the following solution:

    • Set your tenant as the project level property, e.g. tenant
    • Define environment specific stuff within Environment configuration
      • Define two APIs:
        • one for authorization API
        • second for your target API
      • In the endpoints use project-level tenant property (e.g. ${#Project#tenant}) to parametrize the endpoints
      • Grab the token from the authorization response and save it to another project-level property

    When executing the testrunner, use parameters:

    -E to set the environment

    -P to set the tenant (project level variable)

     

    Best regards,

    Karel

     

KarelHusa's avatar
KarelHusa
Champion Level 1

srixon ,

given the details you gave us above I would suggest the following solution:

  • Set your tenant as the project level property, e.g. tenant
  • Define environment specific stuff within Environment configuration
    • Define two APIs:
      • one for authorization API
      • second for your target API
    • In the endpoints use project-level tenant property (e.g. ${#Project#tenant}) to parametrize the endpoints
    • Grab the token from the authorization response and save it to another project-level property

When executing the testrunner, use parameters:

-E to set the environment

-P to set the tenant (project level variable)

 

Best regards,

Karel

 

srixon's avatar
srixon
Occasional Contributor
3 years ago

Hi Karel,

 

Thank you for the suggestions. 

  • I tested adding the parameters to the endpoints and that is working great.
  • I also defined two APIs as you suggested

However, in regards to your last bullet "Grab the token from the authorization response and save it to another project-level property".  At what point do you suggest I do this?  Should this be done in a script that runs at the beginning of the project?  I assume yes, and if so, are there any good script examples?  Hoping that ReadyAPI already has some methods I can use so I do not have to reinvent the wheel. 

 

 

  • KarelHusa's avatar
    KarelHusa
    Champion Level 1
    3 years ago

    srixon ,

    the solution depends on the structure of your tests and also on the authentication methods.

    If you can satisfy the authentication with any method from Auth manager, that would be the easiest way to go.

     

    Otherwise you can e.g. dedicate a test case for authentication. In such test case you can invoke the authentication, process its response and save into a property. You can avoid scripting if you use property transfer test step. Also you can use a Run Test Case step to invoke it wherever needed.

     

    Maybe you can close this thread (which relates to endpoint configuration) and start a new one for authentication if needed.

     

    Best regards,

    Karel