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 Unexpected error during command com.rsa.ucm.request.AddSelfServiceRequestCommand execution when requesting token via-Authe… 192Number of Views Downloading RSA Authentication Manager license files or RSA Software token seed records 2.64KNumber of Views Unable to remove privileges for an RSA Via Governance and Lifecycle user 79Number of Views "Insufficient privileges to view change request" when approver click on the change request number in RSA Identity Governan… 44Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators