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

Active Roles On Demand Hosted - 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 One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect 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 Office 365 Groups Managing Azure Security 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 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: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta

Running an automation workflow on demand

An automation workflow can be configured so that users can run it manually regardless of the schedule. This allows them to start the workflow on demand. One can only run an automation workflow on demand if the workflow is enabled and the Allow the workflow to be run on demand setting is selected in the workflow start conditions. For information about enabling a workflow, see Re-enabling an automation workflow to run. For instructions on how to view or change workflow start conditions, see Configuring start conditions for an automation workflow.

You can run an automation workflow on demand from the Active Roles console or Web Interface.

To run an automation workflow on demand from the Active Roles console

  1. In the Active Roles console tree, under Configuration | Policies | Workflow, right-click the desired automation workflow and click Run.
  2. If prompted, examine or change the values of the workflow parameters.
  3. Click OK in the confirmation message box.

To run an automation workflow on demand from the Web Interface

  1. On the home page in the Web Interface, click Directory Management.
  2. In the TREE pane, expand the Workflow branch and click the container that holds the desired workflow.
  3. In the list of the workflow names, to the right of the TREE pane, click the name of the desired workflow.
  4. Choose the Run command from the menu.
  5. If prompted, examine or change the values of the workflow parameters.
  6. Click OK in the confirmation message box.

Active Roles prompts you for parameter values if the workflow has any parameters that need to be supplied by the user running the workflow on demand. If the workflow has no parameters that require user input, then Active Roles will start the workflow without prompting you for parameter values.

Once you have started an automation workflow, Active Roles opens a run history report, allowing you to examine the progress of workflow execution. The report displays the workflow execution status along with information about the activities performed during workflow run. For a workflow that is in progress you have the option to cancel execution of the workflow by clicking the Terminate button.

Viewing run history of an automation workflow

You can use the run history report to examine the running or completed instances of the automation workflow. The report displays the workflow execution status (success or failure) along with the activities that were performed during each workflow run.

After the workflow is completed, the report retains history information about the workflow run. For each completed run of the workflow, the report allows you to identify when and by whom the workflow was started, when the workflow was completed, and what parameter values were used.

The report also lists the workflow activities that were executed during the workflow run. For each activity, you can determine whether the activity was completed successfully or returned an error. In case of error, the report provides an error description. For activities requesting changes to directory data (for example, activities that create new objects or modify existing objects), you can examine the requested changes in detail by clicking the Operation ID number in the run history report. The report sections have the same contents as with Change History reports (see Workflow activity report sections in the Active Roles Administration Guide).

To view run history of an automation workflow from the Active Roles console

  • In the Active Roles console tree, under Configuration | Policies | Workflow, right-click the desired automation workflow and click Run History.

To view run history of an automation workflow from the Web Interface

  1. On the Home page in the Web Interface, click Directory Management.
  2. In the TREE pane, expand the Workflow branch and click the container that holds the desired workflow.
  3. In the list of the workflow names, to the right of the TREE pane, click the name of the desired workflow.
  4. Choose the Run History command from the menu.

Terminating a running automation workflow

You can terminate a running automation workflow to stop the workflow from completing its actions.

To terminate a running automation workflow

  • Click the Terminate button on the page that displays the automation workflow’s run history.

For instructions on how to access run history, see Viewing run history of an automation workflow.

The Run History page displays both running and completed instances of the automation workflow. The Terminate button is available on each instance that is currently running. After you click the button to terminate a running instance of an automation workflow, you may experience a delay (up to several minutes) before the workflow shuts down.

Terminating a running automation workflow does not roll back or cancel the workflow activities that have already been performed; this only stops the workflow from running the activities that are in progress or not yet started.

Disabling an automation workflow from running

If you want to prevent an automation workflow from running for a certain period of time, you can disable the workflow. The workflow can be enabled at a later time so that it is allowed to run. For more information, see Re-enabling an automation workflow to run.

To disable an automation workflow from running

  • In the Active Roles console tree, under Configuration | Policies | Workflow, right-click the desired automation workflow and click Disable Workflow.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级