You use the advanced OAuth 2.0 settings to define how an access token should be handled.
 |
There are three settings: one of them relates to sending requests, the others relate to refreshing the access token.
The Send Access Token option defines where the access token is sent.
Option | Description | Example |
|---|---|---|
Header | The access token is sent as the request header. |
|
Query | The access token is sent as a query parameter. |
|
The Refresh Access Token option configures whether ReadyAPI updates the expired access token automatically or not.
Tip
Use the Access Token Expiration Time option to configure when ReadyAPI should mark an access token as expired.
Option | Description | |
|---|---|---|
Automatic | (Default) ReadyAPI updates the access token automatically. If the authentication server provides a refresh token, ReadyAPI uses it to get a new access token. Otherwise, ReadyAPI runs automation if it is configured. | |
Manual | You need to update an access token manually. If the authentication server provides a refresh token, you can use it to get a new access token. To do this, click Refresh next to the access token:
NoteThe button is not available if the authentication server does not provide a refresh token. |
The Access Token Expiration Time option defines the expiration time for the access token. You can use the expiration time provided by the server, or you can specify the time you need manually.
Note
The 0 value indicates that the token will never expire. There is no setting for immediate expiration of the token.
Option | Description |
|---|---|
Server | ReadyAPI uses time provided by the authorization server. |
Custom | ReadyAPI marks the token as expired after the specified number of seconds, minutes, or hours elapses. |