Configure Timeout Period for API Tokens

You can configure the timeout period for access tokens and refresh tokens. Use an access token to authenticate yourself when you make an API call. Use a refresh token to generate access tokens.

For information on using tokens to make API calls, see the Authentication topic in the Axon 7.0 Data Governance REST API Guide.

You must have the Super Admin profile to perform this task.

1. From the Axon toolbar, click the Admin Panel menu item under your user name.

2. In the menu on the left, under the Customize & Configure category, click System Settings.

3. In the Group list, select JWT Settings.

4. Click Edit, and configure the following properties:

Property	Description
JWT Validity	Timeout period of the access token. Enter a value in seconds. For example, if you want to set the expiration date for 7 days, enter 604800. The access token expires if you do not use it within the timeout period.
Refresh Token Validity	Timeout period of the refresh token. Enter a value in seconds. For example, if you want to set the expiration date for 30 days, enter 2592000. The refresh token expires if you do not use it within the timeout period. Note: Each time you use a refresh token, the timeout period restarts from the usage date. For example, if you generate a token on June 1 with a timeout period of 60 days, the token will expire on July 30. If you use the token on June 3, the timeout period restarts, and the token will expire on August 2.

Property

Description

JWT Validity

Timeout period of the access token. Enter a value in seconds. For example, if you want to set the expiration date for 7 days, enter 604800. The access token expires if you do not use it within the timeout period.

Refresh Token Validity

Timeout period of the refresh token. Enter a value in seconds. For example, if you want to set the expiration date for 30 days, enter 2592000. The refresh token expires if you do not use it within the timeout period.

Note: Each time you use a refresh token, the timeout period restarts from the usage date. For example, if you generate a token on June 1 with a timeout period of 60 days, the token will expire on July 30. If you use the token on June 3, the timeout period restarts, and the token will expire on August 2.

5. Click Save.

6. In the Linux environment, run the following command to clear the Axon cache and restart the necessary services:

sh <INSTALLATION_DIR>/axonhome/third-party-app/scripts/paramsync

When you run the paramsync script, Axon restarts the HTTPD, Memcached, and email notification services.

Note: When you clear the cache and restart the Axon services, the Axon web interface might be disrupted for some users that are logged into Axon. Informatica recommends that you update the cache after you save your changes in all the System Settings pages. Additionally, perform this action during a maintenance period when very few users are using Axon.