Splunk Observability Cloud recently launched an improved design for the access tokens page for better usability and performance, which was announced here. This release made some important token changes that offer greater flexibility to control your default org token expiry with longer expiry dates.
Prior to this release, org tokens' default expiry was 365 days. This has been shortened to 30 days for enhanced security. However, we understand this might be inconvenient in some cases. To mitigate this change, we also released the ability for customers to make a one-time change to update their default 30-day expiry from the global settings page. To summarize, the following changes have been added:
1. Default expiry:
- The default token expiry for org tokens is now 30 days (formerly 365 days).
- This default expiry value can be changed to x days (up to 18 years) based on customer choice from the General Settings page accessible to admin role.
- Once this value is changed, all new tokens created will use this value as the default expiry.
2. Token expiry at the time of setting up new tokens
- At the time of setting up a new token, customers have a choice of changing the token expiry of that specific token to any value up to 18 years.
3. Token expiry at the time of token rotation
- At the time of token rotation, customers can change expiration date to any value up to 18 years from the time of token rotation.
