Privileges for Request Approvers and Token Distributors
Request Approvers and Token Distributors can change the type of token requested by users. For example, they can change a request for a keyfob token to a request for a USB token.
Request Approvers and Token Distributors cannot:
Change hardware token requests to software token requests, or the reverse.
Change requests for the on-demand tokencode service to hardware or software token requests, or the reverse.
RSA recommends that Request Approvers and Token Distributors do not change a request for a keyfob to a PINPad-style token because the PIN for a keyfob is not compatible with the PINPad-style token and the PIN fails when users try to use it.
If you change the PIN policy, verify that it does not affect any of the pending token requests. RSA recommends that you take appropriate action on pending requests before you change the PIN policy for any tokens.
For Token Distributor workflow instructions, see Complete User Requests.
Related Articles
Scope for Request Approvers and Token Distributors 10Number of Views Provisioning 2Number of Views Using E-mail Notifications for Provisioning Requests 43Number of Views Workflow for Provisioning Requests 16Number of Views Approve and Reject User Requests 22Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle