can a softtoken that has reached the expiration date still be extended?
can a softtoken that has reached the expiration date still be extended?
Hello Dan,
Kindly note that any active or expired software tokens that were distributed in an Authentication Manager version earlier than version 8.2 can not be extended, however the Software tokens that are expired and were distributed in RSA Authentication Manager 8.2 or later can be extended with no issues.
And kindly find the below links for more details about this feature:
Software Token Lifetime Extension
Extend Software Token Lifetimes
Best Regards,
Ahmed Abouelnaga
@Ahmed: You forgot a word.
Kindly note that any active or expired software tokens that were distributed in an Authentication Manager version earlier than version 8.2 can NOT be extended.
Yes. As long as the token was distributed from 8.2 or higher, you can extend 'any old token'. For example I loaded up seed records from 2004, and distributed some software tokens from 8.4.0.9.0. The end user sees the token expires in 2035, and it looks like it is working on user side (the token generates codes but authentications end up failing and user won't know why). On RSA Authentication Manager, the token is expired in 2004 and won't authenticate at all. But I can go find a current software token that has some life left in it (I have some new ones that expire in 2022) and I can now go extend that old token from 2004, and it now shows a new expire date in 2022, and works for authentication.
The only rule here is: the token needs to be distributed from version 8.2.0.0.0 or higher, so it ends up in the user device with the 'artificial' expire date of 2035, and the real expire date is only seen on the Authentication Manager server. Any distributed version prior to 8.2 will stamp the end user copy of the token with the actual expire date (in my case 2004) and won't work at all on the user side.
Yes. As long as the token was distributed from 8.2 or higher, you can extend 'any old token'. For example I loaded up seed records from 2004, and distributed some software tokens from 8.4.0.9.0. The end user sees the token expires in 2035, and it looks like it is working on user side (the token generates codes but authentications end up failing and user won't know why). On RSA Authentication Manager, the token is expired in 2004 and won't authenticate at all. But I can go find a current software token that has some life left in it (I have some new ones that expire in 2022) and I can now go extend that old token from 2004, and it now shows a new expire date in 2022, and works for authentication.
The only rule here is: the token needs to be distributed from version 8.2.0.0.0 or higher, so it ends up in the user device with the 'artificial' expire date of 2035, and the real expire date is only seen on the Authentication Manager server. Any distributed version prior to 8.2 will stamp the end user copy of the token with the actual expire date (in my case 2004) and won't work at all on the user side.