Workflow for Provisioning Requests
Provisioning uses workflows to automate token deployment. A workflow defines the number of steps or work tasks required for each type of user provisioning request. The users and administrators who perform tasks in a workflow are called workflow participants.
The following table lists the types of workflow participants and the tasks they can perform.
Workflow Participant | Tasks |
User | From the Self-Service Console, the user initiates a request that starts a workflow. The types of user requests are:
|
Request Approver | From the Security Console, the Request Approver:
|
Token Distributor | From the Security Console, the distributor:
|
Assigning Administrative Roles
If you use workflows for provisioning requests, you need to assign the Token Administrator, Request Approver, and Token Distributor Administrator roles. For more information about administrative roles in provisioning, see Administrative Roles in Provisioning. For instructions, see Assign an Administrative Role.
Related Concepts
Related Articles
Requests Pending Submissions queue accumulating in RSA Identity Governance & Lifecycle 188Number of Views Silent discard of authentication requests in RSA Authentication Manager 8.0 and 8.1; Authentication fails without log entry 209Number of Views Clicking on the 'View the Approval Request' URL from an approval email fails with 'Request could not be handled' in RSA Id… 83Number of Views Approve and Reject User Requests 22Number of Views Request could not be handled error in RSA Identity Governance & Lifecycle Request Forms 106Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory