- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can i turn off the token expiration notification
Is there a way to turn off the notice about the token expiring in 30 days> we have several customers who are uncomfortable about getting this notice. We plan to renew all of the tokens in BULK.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately it is not configurable. Depending on the use cases you could look at leveraging other multi-factor authentication options available through the cloud authentication service that are subscription based and non-expiring.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately it is not configurable. Depending on the use cases you could look at leveraging other multi-factor authentication options available through the cloud authentication service that are subscription based and non-expiring.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rafael,
Yeah you can't really turn this off with what you have now, but planning for the same thing in the future means basically you want extendable software tokens, which is something available in 8.2 and later. Extendable soft tokens means that the date when a token no longer works is controlled at the AM server side, so the imported token in your smart phone or PC 'thinks' it does not expire until 2035. If it expires on the AM server side, your user is simply going to fail authentication.
You have to be at 8.2 when you distribute these software tokens. You're allowed to buy a token authenticator (soft token) that you only have to distribute once, in AM 8.2 or higher, and if that person with that software token is still with in x number of years in the future when the token expires, you can extend its life in your AM server, and not have to redistribute and import it into the user device.
It's basically a way to tie an expiration date to a token serial number on the fly, instead of only in the Token Seed record.
