- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Extendable Software Tokens
Question on Extendable Software Tokens
Recently, on Sept 25th we upgraded from 8.1 sp1 to 8.2.0
Just prior to the upgrade we imported new software tokens.
After the upgrade, we noticed some of the new and old sw tokens are marked as "Extendable" whereas others are not.
Trying to understand why some of them have ‘extendable’ listed and others do not.
I've read and understand the RSA document " Software Token Lifetime Extension" but it doesn't explain why some of the older software tokens (which are not expiring anytime soon) are also tagged as "Expandable" yet the new ones recently installed just prior to the upgrade to 8.2 are not but some are. Is there a document which explains the details on how and when and under which circumstances will an old or new sw token will be tagged as Expandable or have I run into a bug.
I understand the default value of 15 days can be changed by following the Configure Software Token Extension Parameters.
Here is an example of what I'm seeing:
If I view all assigned software tokens, i see for instance a token that was imported in Nov of 2013 and assigned to a user in April of 2014, and the token expires Dec 2016. (clearly this is an older token yet it is marked as Extendable)
- Tags:
- 8.1
- 8.2
- AM
- Auth Manager
- Authentication Manager
- Authenticator
- Authenticators
- Community Thread
- Discussion
- extendable software tokens
- Forum Thread
- RSA SecurID
- RSA SecurID Access
- SecurID
- Token
- Token Auth
- Token Authentication
- Token Authenticator
- Token Authenticators
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mark,
Unless the token has been issued from the 8.2 system you won't see the extendable option......Software tokens that have been distributed in AM 8.2 only are eligible for extension. An already distributed token in AM 8.1Sp1 will not be extendable. The admin is required to re-distribute the token in AM 8.2 for the token to be extendable.
Note: Software evaluation tokens cannot be extended or used for extension
Software evaluation tokens - are token generated during deployment of evaluation license
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mark,
I have moved this thread to the https://community.rsa.com/community/products/securid?sr=search&searchId=98fcdf0b-65be-4281-ba50-41e4a97a5e34&searchIndex=0 page so that you can get an answer to your question.
Thanks,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mark,
Unless the token has been issued from the 8.2 system you won't see the extendable option......Software tokens that have been distributed in AM 8.2 only are eligible for extension. An already distributed token in AM 8.1Sp1 will not be extendable. The admin is required to re-distribute the token in AM 8.2 for the token to be extendable.
Note: Software evaluation tokens cannot be extended or used for extension
Software evaluation tokens - are token generated during deployment of evaluation license
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We migrated from 7.x to 8.1sp1 in March of 2015.
We have 200 sw tokens that were issued in Nov of 2013 that are expiring this Dec 2016, when our system was at 7.x.
We recently updated from 8.1 sp1 to 8.2.0 last weekend, 9/25/2016.
These tokens show up as extendable. Can they be re-used even though they were not issued by 8.2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If they weren't issued in 8.2 then they would not be extendable. However you could issue them from 8.2 to allow them to become extendable. This however would require reloading the newly issued token onto whatever devices currently use software tokens.
