立即与支持人员聊天
与支持团队交流

Active Roles 8.0 LTS - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Workflows
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Microsoft 365 Groups Managing Azure Security Groups Managing cloud-only distribution groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes Managing cloud-only shared mailboxes
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server Replication Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta Active Roles Language Pack

Initiator conditions

The initiator conditions specify:

  • The identity of an operation requestor (initiator), such as a user or group; the workflow starts only if an operation is requested by that identity.
  • A container, such as an organizational unit or Managed Unit; the workflow starts only if an operation requests changes to, or creation of, an object in that container.

To view or change the initiator conditions

  1. In the Change Workflow Options and Start Conditions dialog box, go to the Conditions tab, and observe the list in the Initiator Conditions area.

    Each entry in the list represents a single initiator condition, with the first field identifying the operation requestor and the second field identifying the container. If the list is missing, no initiator conditions are defined.

  1. To define an initiator condition:
    1. Click Add in the Initiator Conditions area.
    2. Populate the list of operation requestors.
    3. Select the container.
  2. To delete an initiator condition, select the corresponding entry from the Initiator Conditions list, and click Remove.

If multiple initiator conditions are defined, the workflow starts if any one of them is fulfilled.

If multiple operation requestors are defined within a single initiator condition, the condition is considered fulfilled if the operation is requested by any one of those identities.

Filtering conditions

A filter can be used to define any additional conditions on objects involved in an operation. The workflow starts only if the operation satisfies those conditions. If no filter is set, then no additional conditions are in effect.

When you configure a filter, you need to add at least one condition, but you are not limited in the number of conditions that you can add. You can add, delete, and group conditions using various operators. It is possible to nest condition groups within other condition groups to achieve the results that you want.

A condition group contains one or more conditions connected by the same logical operator. By grouping conditions, you specify that those conditions should be evaluated as a single unit. The effect is the same as if you put parentheses around an expression in a mathematical equation or logic statement.

By default, a single condition group is created when you add a condition. You can create additional condition groups to group a set of conditions and nest grouped conditions within other condition groups.

In a condition group, conditions are connected using the AND, OR, NOT AND, or NOT OR logical operator:

  • AND group evaluates to TRUE if all conditions in the group are TRUE.
  • OR group evaluates to TRUE if any condition in the group is TRUE.
  • NOT AND group evaluates to TRUE if any condition in the group evaluates to FALSE.
  • NOT OR group evaluates to TRUE if all conditions in the group evaluate to FALSE.

By default, AND is the logical operator between the conditions in a condition group. It is possible to change the logical operator by converting the condition group to a different group type.

When you add a condition, the workflow designer first prompts you to specify what you want the condition to evaluate. The following options are available:

  • Property of workflow target object.  This option is intended to evaluate the value of a certain property of the target object of the request that started the workflow. You can select the desired property when you configure a condition.
  • Property of workflow initiator.  This option is intended to evaluate the value of a certain property of the user whose request started the workflow. You can select the desired property when you configure a condition.
  • Changed value of workflow target object property.  This option is intended to evaluate the value that is requested to be assigned to a certain property of the workflow target object, which represents the requested change to the property of the target object of the request that started the workflow. You can select the desired property when you configure a condition.
  • Workflow parameter value.  This option is intended to evaluate the value of a certain parameter of the workflow. You can select the desired parameter from the workflow definition when you configure a condition.
  • Property of object from workflow data context.  This option is intended to evaluate the value of a certain property of the object that will be selected on the basis of the data found in the workflow environment at the time of evaluating the workflow start conditions. When you configure a condition, you can choose the desired property and specify which object you want the workflow engine to select upon evaluating the condition at workflow start time.
  • Value generated by rule expression.  This option is intended to evaluate the string value of a certain rule expression. By using a rule expression, you can compose a string value based on properties of various objects found in the workflow environment at the time of evaluating the workflow start conditions. The workflow engine calculates the value of your rule expression upon evaluating the condition at workflow start time.

Once you have specified the entity or field that you want the condition to evaluate, you can choose a comparison operator and specify a comparison value. The comparison operator determines the operation of comparing the entity or field to evaluate with the comparison value you specified, and causes the condition to evaluate to TRUE or FALSE depending on the outcome of that operation.

You can choose from the following options to specify a comparison value:

  • Text string.  Performs comparison with a literal string of characters. You can type the desired string when you configure a condition.
  • Property of workflow target object.  Performs comparison with the value of a certain property of the target object of the request that started the workflow. You can select the desired property when you configure a condition.
  • Property of workflow initiator.  Performs comparison with the value of a certain property of the user whose request started the workflow. You can select the desired property when you configure a condition.
  • Changed value of workflow target object property.  Performs comparison with the value that is requested to be assigned to a certain property of the workflow target object, which represents the requested change to the property of the target object of the request that started the workflow. You can select the desired property when you configure a condition.
  • Workflow parameter value.  Performs comparison with the value of a certain parameter of the workflow. You can select the desired parameter from the workflow definition when you configure a condition.
  • Property of object from workflow data context.  Performs comparison with the value of a certain property of the object that will be selected on the basis of the data found in the workflow environment at the time of evaluating the workflow start conditions. When you configure a condition, you can choose the desired property and specify which object you want the workflow engine to select upon evaluating the condition at workflow start time.
  • Value generated by rule expression.  Performs comparison with the string value of a certain rule expression. By using a rule expression you can compose a string value based on properties of various objects found in the workflow environment at the time of evaluating the workflow start conditions. The workflow engine calculates the value of your rule expression upon evaluating the condition at workflow start time.

Steps to configure filtering conditions

The Change Workflow Options and Start Conditions dialog box provides a condition builder for configuring a filter specific to workflow start conditions, located in the Filtering Conditions area on the Conditions tab. You can access the condition builder in the box under the Workflow starts only if these conditions are fulfilled heading.

When you configure a filter, you need to add at least one condition. Initially, you add a condition to the default condition group. You can create additional condition groups to group a set of conditions and nest grouped conditions within other condition groups.

A condition group contains one or more conditions connected by the same logical operator. By grouping conditions, you specify that those conditions should be evaluated as a single unit. The effect is the same as if you put parentheses around an expression in a mathematical equation or logic statement.

To add a condition to a condition group

  • In the condition builder, click the name of the condition group and then click Insert condition.

Click the plus sign (+) next to the name of the condition group.

You can remove a condition, if needed, by clicking the Delete condition button labeled X on the right side of the list item representing the condition in the condition builder.

To add a condition group into another condition group

  • Click the name of the condition group, point to Insert condition group, and then click an option to specify the logical operator:
    • AND group.  The condition group evaluates to TRUE if all conditions in the group are TRUE.
    • OR group.  The condition group evaluates to TRUE if any condition in the group is TRUE.
    • NOT AND group.  The condition group evaluates to TRUE if any condition in the group evaluates to FALSE.
    • NOT OR group.  The condition group evaluates to TRUE if all conditions in the group evaluate to FALSE.

By default, AND is the logical operator between the conditions in a condition group. It is possible to change the logical operator by converting the condition group to a different group type: Click the name of the group, point to Convert condition group to, and then click the option appropriate to the desired logical operator.

You can remove an entire condition group, if needed, by clicking the name of the group and then clicking Delete condition group.

Once you have added a condition to a condition group, you can use the following steps to configure the condition.

To configure a condition

  1. Click Configure condition to evaluate, and then choose from the following options to specify the entity or field you want the condition to evaluate:
    • Click Property of workflow target object to evaluate a certain property of the workflow target object. Then, click to choose the target property.
    • Click Property of workflow initiator to evaluate a certain property of the workflow initiator. Then, click to choose the target property.
    • Click Changed value of workflow target object property to evaluate requested changes to a certain property of the workflow target object. Then, click to choose the target property.
    • Click Workflow parameter value to evaluate the value of a certain parameter of the workflow. Then, click to choose the desired parameter.
    • Click Property of object from workflow data context to evaluate a certain property of a certain object involved in the workflow. Then, click to choose the target object and the target property.
    • Click Value generated by rule expression to evaluate the string value generated by a certain rule expression. Then, click to add entries to the rule expression.
  2. Click the current comparison operator, if needed, and then click the operator you want the condition to use.

    By default, a condition is configured to use the equals operator.

  1. Click Define value to compare to, and then choose from the following options to specify the desired comparison value:
    • Click Text string to performs comparison with a literal string of characters. Then, type the desired string.
    • Click Property of workflow target object to perform comparison with the value of a certain property of the workflow target object. Then, click to choose the target property.
    • Click Property of workflow initiator to perform comparison with the value of a certain property of the workflow initiator. Then, click to choose the target property.
    • Click Changed value of workflow target object property to perform comparison with the value that is requested to be assigned to a certain property of the workflow target object. Then, click to choose the target property.
    • Click Workflow parameter value to perform comparison with the value of a certain parameter of the workflow. Then, click to choose the desired parameter.
    • Click Property of object from workflow data context to perform comparison with the value of a certain property of a certain object involved in the workflow. Then, click to choose the target object and the target property.
    • Click Value generated by rule expression to perform comparison with the string value generated by a certain rule expression. Then, click to add entries to the rule expression.

Configuring script-based conditions

To configure a script-based condition, you need to create and apply a script module containing a function that analyzes the requested operation to determine whether to start the workflow. The function may use the Active Roles ADSI Provider to access properties of objects involved in the operation, analyze the properties, and return TRUE or FALSE depending on the result of the analysis. The workflow starts if the function returns TRUE.

To apply a script-based condition

  1. In the condition builder, click the name of the condition group, and then click Insert condition.
  2. Click Configure condition to evaluate, and then click Value generated by rule expression.
  3. In the Configure Rule Expression dialog box, click Add entry and then click Value generated by script.
  4. Use the Configure Entry dialog box to select the appropriate script module and script function.
  5. Click OK to close the Configure Entry dialog box.
  6. Click OK to close the Configure Rule Expression dialog box.
  7. In the condition builder, verify that comparison operator equals is selected.
  8. Click Define value to compare to, and then click Text string.
  9. In the Configure Entry dialog box, under Text string, type TRUE.
  10. Click OK to close the Configure Entry dialog box.
  11. Click OK to close the Change Workflow Options and Start Conditions dialog box.
  12. Save your changes to the workflow definition.

As a result of these steps, the workflow will start if the function specified in Step 4 returns TRUE upon evaluating the condition at workflow start time.

For more information and instructions, see “Developing Script Condition Functions” in the Active Roles SDK documentation.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级