<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7VEeSANOkta Classic EngineAdministrationAnswered2018-09-05T01:27:50.000Z2017-06-12T17:19:15.000Z2017-06-12T17:19:15.000Z

JessicaW.72146 (Customer) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
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:

0EM2A000000cBtI
  • 1 answer
  • 785 views

  • marc.johnston1.4609982285157063E12 (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?
This question is closed.
Loading
Self Service Token Showing Expired Event Immediately After Creation in Logs