Automations
Overview: Automating Identity & Credential Management
The IDMS empowers organizations to significantly reduce manual effort by automating a wide range of device and credential management tasks. This automation leads to more efficient operations and an enhanced user experience.
For example, when a user's certificate is issued or updated, IDMS can automatically register it with all necessary "relying parties" (systems that trust the certificate, such as a computer logon system or a physical access control system). This means a user's Multi-Factor Authentication (MFA) device becomes immediately usable for computer access or opening doors, without any manual intervention.
Automation Rule Components
IDMS uses a set of clearly defined components to build and execute these powerful automation rules:
Automation Trigger (Event): This is the high-level IDMS system activity or category that initiates an automation process. Examples include activities related to Identity Proofing (verifying a user's identity), Credentialing (issuing or updating credentials), or general Management Events (e.g., a user's status change).
Specific Transaction Type: Within an "Automation Trigger," this defines the precise, detailed action that must occur for the rule to fire. For instance, if the "Automation Trigger" is "Credentialing," a "Specific Transaction Type" could be "Certificate Activated," "Credential Revoked," or "Device Registered."
IDMS Response (Action): This is the specific action that the IDMS system will automatically perform once both the "Automation Trigger" and "Specific Transaction Type" conditions are met.
Response Destination (System): This defines where the result of the IDMS Response is sent or applied. This could be:
An email notification to an administrator or user.
An update sent to a relying party system (e.g., an access control system, a directory service).
An internal IDMS function (e.g., updating a user's status within IDMS itself).
Running an Automation
The automation will be executed when based on the trigger. For example, if the automation rule specifies and Credential trigger with an Activated action type, the respective automation rule will run when a credential is activated.
Running the Automation Retroactively
In the case automation needs to run after the event has occurred (for example, to synchronize all issued credentials with a relying party database), the Reconciliation process can be performed.