Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit ef52818

Browse files
Merge branch 'main' into mbechtold-final-token-validity-change
2 parents 3c4c443 + 00a9141 commit ef52818

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

admin/authentication/authentication-tokens/org-tokens.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Power users who have access to tokens in an organization see a banner, but only
2222
Token expiry
2323
================
2424

25-
You can view the expiration dates of your tokens through the access token page. To view this page, select :guilabel:`Settings` and select :guilabel:`Access tokens`. By default, access tokens expire 18 years after the creation date. You can rotate a token before it expires, or you can change the default expiration date during token creation. For details, see :ref:`access-token-rotate` and :ref:`create-access-token-date`.
25+
You can view the expiration dates of your tokens through the access token page. To view this page, select :guilabel:`Settings` and select :guilabel:`Access tokens`. By default, access tokens expire 30 days after the creation date. You can rotate a token before it expires, or you can change the default expiration date during token creation. For details, see :ref:`access-token-rotate` and :ref:`create-access-token-date`.
2626

2727
By default, every organization admin receives an email 30 days before a token in their org expires. The email includes a link to Splunk Observability Cloud that displays a list of expiring tokens. To change the expiration reminder date, see :ref:`create-access-token-date`.
2828

0 commit comments

Comments
 (0)