We have some areas of pain around RSA token distribution and would like to leverage self-service to streamline some of our processes. For example, when a user gets a new PC, or loses their phone they need their token redistributed. Is there a feature in self-service functionality allow the user to get this on their own? Also, when a new user comes on board, what functionality is available to have a token/activation code automatically distributed via self-service?
Thank you,
Jim
Re-distribute is not an option.
Replacement, or new token, or a temporary emergency tokencode are available.
If a user has a token already, but it is misplaced...you can enable the troubleshooting options
on the self-service console, and a user can access these options and get something like a temporary emergency token code.
-----------------------
If you want to be able to give out new tokens and not just temporarily work around a misplaced token....
You need provisioning options to be available when you check security console, setup, self-service settings.
For a new token...or replacement token
Typically users request a new software token of a particular type, set up a new pin for it ahead of time...and wait for an admin to approve the request. Then once approved, the user gets an email with a token attached, or a ctkip link. Users typically access self-service for the first time using ldap password, then they pre-set
a series of life-questions for later use for [troubleshooting tokens if needed]. Then once in, they can request a new token.
Some config options you need to investigate (use the security console help menu for details):
security console, setup, self service settings
a) manage authenticators - here you pick what type of software token is available in self service (based on software token profiles already built)
b) workflow polices - here you determine how many admins need to be involved with approving the request before a token is distributed
c) enable or disable self-service features - enable provisioning and any other options
Re-distribute is not an option.
Replacement, or new token, or a temporary emergency tokencode are available.
If a user has a token already, but it is misplaced...you can enable the troubleshooting options
on the self-service console, and a user can access these options and get something like a temporary emergency token code.
-----------------------
If you want to be able to give out new tokens and not just temporarily work around a misplaced token....
You need provisioning options to be available when you check security console, setup, self-service settings.
For a new token...or replacement token
Typically users request a new software token of a particular type, set up a new pin for it ahead of time...and wait for an admin to approve the request. Then once approved, the user gets an email with a token attached, or a ctkip link. Users typically access self-service for the first time using ldap password, then they pre-set
a series of life-questions for later use for [troubleshooting tokens if needed]. Then once in, they can request a new token.
Some config options you need to investigate (use the security console help menu for details):
security console, setup, self service settings
a) manage authenticators - here you pick what type of software token is available in self service (based on software token profiles already built)
b) workflow polices - here you determine how many admins need to be involved with approving the request before a token is distributed
c) enable or disable self-service features - enable provisioning and any other options