Soft token expiration date is more then 15 years is this normal?
We have several soft tokens that have a exasperation of more then 15years and the rest have a normal expiration of one year, is this glitch in the system or is this a normal function?
If this is a normal function is there an added cost associated with the extend length?
If this is normal can we extend our existing tokens or will they need to be replaced?
- Auth Manager
- Authentication Manager
- Community Thread
- Forum Thread
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
Are you seeing this on the Software Token Application or in the AM server?
If on the AM Server, these are called Subscription tokens and technically they last as long as it says they last in the Security Console - Not in the Software Token Application. Since AM 8.2, Token expiration is controlled completely at the AM server side, there is no "agreement" necessary with the imported token on the software app on the Windows Desktop or smart phone. This allows tokens to be extended on the AM server. That is what you have to check.
Subscription tokens are basically soft tokens with a really far out expiration date, but Sales charges your company a subscription fee each year, so you do not pay all up front. I imagine Sales has ways to enforce this through a company's support contract, but technically they would keep working until they expired.