Token Expiration Question Skip to main content
https://support.okta.com/help/answers?id=906f0000000hzvciac&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:
Wayne KalseyWayne Kalsey 

Token Expiration Question

Hello,

We have OKTA integrated with Active Directory.  Everything has been working properly.

I noticed under SECURITY - API, that the Okta AD Agents are using  Tokens.  These tokens look like they are going to expire in early March according to the API console in Okta.

Will I need to do anything to prevent this from not working?  This would prevent our AD users from logging into OKTA.  Do the tokens automatically renew themselves?

Any input would be greatly appreciated to prevent down time.
Best Answer chosen by Wayne Kalsey
Raja NejemRaja Nejem (Okta, Inc.)
API tokens are valid for 30 days and automatically renew every time they are used with an API request. When a token has been inactive for more than 30 days it is revoked and cannot be used again. 

All Answers

Raja NejemRaja Nejem (Okta, Inc.)
API tokens are valid for 30 days and automatically renew every time they are used with an API request. When a token has been inactive for more than 30 days it is revoked and cannot be used again. 
This was selected as the best answer
Wayne KalseyWayne Kalsey
Excellent.  Thank you.
Pallavi ThotaPallavi Thota
We have created a token last year on May 3rd  2016 and its expiration date is on June 22nd 2017.
The recently created token(on May 11th 2017) its expiration date is June 28th 2017 , if this tokens lifetime is 30 days then the expiration date in OKTA should get displayed as June 10th 2017.
 
Please let me know why the expiration date for the last years token(which was created on May 3rd 2016) is getting displayed as June 22nd 2017.
 
Also let me know why the expiration date for token created on May 11th 2017 is getting displayed as June 28th 2017 instead of June 10th 2017.