Creating Multiple Requests and Archiving Requests
If you need to create multiple requests, you can use the User Groups and Token Bulk Requests utility, import-bulk-request. For example, if you want every salesman in your organization to receive a SecurID token, you can create a bulk request on their behalf. The system acts as if each salesman made a separate request using the Self-Service Console.
If you want to free up disk space, you can use the Archive Requests utility, archive-ucm-request, to export closed Self-Service Console requests with their associated attributes and process data. If you need to retrieve the information, you can use the Archive Requests utility to import the archived requests. For example, you might want to resend an approval e-mail to a user who has lost the approval e-mail that contained a token file.
Related Tasks
Related Articles
Attribute Synchronization sometimes updates attributes with attribute variable names instead of attribute values in RSA Id… 85Number of Views How approval activity behaves when change request items are grouped by category in RSA Identity Governance & Lifecycle 123Number of Views When the Escalations column is included in the Change Requests table display, Change Requests with Escalations display as … 40Number of Views AFX: Provisioning access to users sporadically fails yet CRs show100 percent fulfilled in RSA Identity Governance & Lifecycle 75Number of Views How to stop RSA Via Lifecycle & Governance (IMG) review items from reverting back to the default state after a change requ… 103Number 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