Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.9 Security Configuration Guide

Configure REST API token lifespans

This topic describes PowerProtect Data Manager REST API tokens and the default token expiry intervals. These steps also change the behavior of the REST API token expiry mechanism.

About this task

The REST API uses two separate types of tokens: access and refresh. Access tokens are bearer tokens that authenticate REST API calls. Refresh tokens provide enough information to get a new access token after the access token expires.

Using refresh tokens enables you to set shorter lifespans on access tokens without causing frequent credential requests. Shorter access token lifespans reduce the risk of compromised token values. The OAuth Authorization Framework provides more information about token types.

The default time unit is MINUTES. Available time units include: DAYS, HOURS, MINUTES, MONTHS, SECONDS, and WEEKS.

The default access token expiry time is 480. The default refresh token expiry time is 1440.

Steps

  1. Connect to the PowerProtect Data Manager console as an admin user.
  2. Using a Linux text editor, open /usr/local/brs/lib/aaa/config/application-server-custom.properties.
  3. Modify the following properties:
    PropertyDescription
    aaa.jwt.token.chrono-unit The unit for the expiration time properties.
    aaa.jwt.token.access-expiration-time The amount of time after which access tokens expire.
    aaa.jwt.token.refresh-expiration-time The amount of time after which refresh tokens expire.
  4. Save and close the file.
  5. Apply the new configuration:
    aaa restart

  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\