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 9Number of Views Downloading RSA Authentication Manager license files or RSA Software token seed records 2.46KNumber of Views Using E-mail Notifications for Provisioning Requests 39Number of Views "Insufficient privileges to view change request" when approver click on the change request number in RSA Identity Governan… 43Number of Views How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device 673Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x