Imported tokens are showing wrong expiration date in RSA Software Token.
In RSA Authentication Manager the token has an expiration date 11/30/23.
In Software Token it shows 12/31/2035.
RSA Authentication Manager in version 8.4 P 14
RSA Software Token in version 5.0.0.292 or 5.0.2.440 (same)
Token distributed in the past are showing the correct expiration date. I can not say at which point this has changed.
That is to facilitate extending token dates. End user never sees it expire until 2035...admins do see it expire on the paid-for date. An admin can extend the date with another new token, and it will then have a new expire date in SC, but 2035 on end user device and end users don't need to install a new token every time the 'paid for expiration passes'... easing end user frustration with loading new tokens.
But token will expire on the date the Security Console shows unless you buy more tokens and extend them (or just distribute the new tokens but that involves each end user again).
Extending tokens is optional, but for huge deployments it was designed to cut down interruptions and issues installing new tokens for each user every expiration interval. Now, only one admin needs to be involved, instead of every user.