Self Service Token Showing Expired Event Immediately After Creation in Logs Skip to main content
https://support.okta.com/help/answers?id=9062a000000xzr1qag&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Jessica WooleyJessica Wooley 

Self Service Token Showing Expired Event Immediately After Creation in Logs

When reviewing our logs, I've noticed that there are a few self-service events that are immediately followed by that token being expired. The users are active, and the token expiration is set to 1 hour. It doesn't seem to actually expire the password, since some of those events are followed by the user utilizing the token, but I'm curious why the logs may be reporting this.  Thoughts?

Example:
User-added image
Marc JohnstonMarc Johnston (Okta, Inc.)
You can examine the token by calling /introspect to check if the token is still active. There is an expiration date timestamp on the token to compare against the active event you see. Okta doesn't revoke the access token unless you manual call the /revoke. Could you provide some more details on the Self Service event you are performing and some examples of the logs you see?