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 Number of Views Approve and Reject User Requests Number of Views 'Exception checking for internal table usage in collectors' and 'java.lang.NullPointerException' errors when generating a … Number of Views Change requests provisioned by AFX remain in "pending action" or "pending verification" in RSA Governance & Lifecycle Number of Views RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Release Notes: Cloud Access Service and Authenticators RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
