Chat now with support
Chat mit Support

Active Roles 7.5.4 - 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

Changing an existing Policy Type object

You can change an existing Policy Type object by changing the general properties, script, or icon. The general properties include the name, display name, and description. The Policy Type objects are located under Configuration/Server Configuration/Policy Types in the Active Roles console.

The following table summarizes the changes you can make to an existing Policy Type object, assuming that you have found the object in the Active Roles console.

Table 62: Policy Type object changes

To change

Do this

Commentary

Name of the object

Right-click the object and click Rename.

The name is used to identify the object, and must be unique among the objects held in the same Policy Type container.

Display name or description

Right-click the object, click Properties and make the necessary changes on the General tab.

Changing the display name also changes the name of the activity type in the Workflow Designer. You may need to refresh the view in the Workflow Designer for the new name to be displayed.

Script Module

Right-click the object, click Properties, click the Script tab, click Browse, and then select the Script Module you want.

You can change the script in the Script Module that is currently associated with the Policy Type object instead of selecting a different Script Module. To view or change the script, find and select the Script Module in the Active Roles console tree, under Configuration/Script Modules.

Changing the script affects all the existing workflow activities of this type. If you add an activity to a workflow and then change the script for the Policy Type object based on which the activity was created, the activity will run the changed script.

Function to run

Right-click the object, click Properties, click the Script tab, and then choose the appropriate function from the Function to run list.

Changing this setting causes the activities of this type to run function you have selected.

Changing the function does not affect the existing activities of this type. If you add a new activity of this type, the activity will run the new function.

Workflow category

Right-click the object, click Properties, click the Script tab, and then choose the appropriate option from the Use in list.

This setting determines the workflow category (change workflow, automation workflow, or any workflow) in which the activity of this type is allowed. After you have changed this setting, an activity of this type can only be added to the corresponding workflow category. Thus, if you select the Change workflow option, the activity of this type cannot be added to an automation workflow.

Function to declare parameters

Right-click the object, click Properties, click the Script tab, and then choose the appropriate function from the Function to declare parameters list.

Changing this setting changes the list of the activity parameters specific to this activity type. The changes do not affect the parameters of the existing activities of this type. When you add a new activity of this type, the list of the activity parameters is built using the new function to declare parameters.

Policy Type icon

Right-click the object, click Properties, click the Script tab, click Policy Type Icon, and then do one of the following:

  • Click Change and open an icon file containing the image you want.
  • Click Use Default Icon to revert to the default image.

Changing this setting changes the image that appears next to the display name of the activity type in the Workflow Designer, on the pane located next to the workflow process diagram.

Using Policy Type containers

You can use a Policy Type container to store related Policy Type objects and other Policy Type containers.

Containers provide a means for additional categorization of custom activity types, making it easier to locate and select an activity type in the Workflow Designer. The activities toolbox next to the workflow process diagram lists the custom activity types along with the containers that hold the respective Policy Type objects. To prevent containers from cluttering the activities toolbox, the Workflow Designer displays only the containers that are direct descendants of the Policy Types container, and disregards the lower-level containers. To clarify this behavior, let us consider a path to a Policy Type object such as Policy Types/Container A/Container B/Object C. In this case, the Workflow Designer only displays Container A and the activity type C under Container A, disregarding Container B.

To create a new Policy Type container

  1. In the console tree, under Configuration/Server Configuration/Policy Types, right-click the Policy Type container in which you want to create a new container, and select New | Policy Type Container.

    For example, if you want to create a new container in the root container, right-click Policy Types.

  1. In the New Object - Policy Type Container wizard, type a name and, optionally, a description for the new container.

    The name of the container will be displayed in the Workflow Designer if the container is located directly in the Policy Types container.

  1. Click Next and follow the steps in the wizard to complete the creation of the new container.

Exporting activity types

You can export Policy Type objects so that the definition of the activity types is stored in an XML file which can be imported in a different Active Roles environment. Exporting and then importing Policy Type objects make it easy to distribute custom activity types to other environments.

To export a Policy Type object or container

  • Right-click the Policy Type object or container in the Active Roles console, click Export and then specify an XML file to hold the export data.

You can select multiple Policy Objects to export, or you can select a container to export all Policy Type objects and containers held in that container. In either case, the Export operation creates a single XML file that can later be imported to any container under the Policy Types node.

Export of Policy Type objects creates an XML file representing both the objects and the Script Modules containing the scripts for each activity type being exported. During an import, Active Roles creates the Policy Type objects and the Script Modules based on the data found in the XML file. As a result of the import, the activity types are replicated to the new environment and can be used the same way as in the environment from which they were exported.

Importing activity types

You can import the exported Policy Type objects and containers, which will add them to a Policy Type container and allow you to configure and use custom activities defined by those Policy Type objects. All the data required to deploy the activity types is represented in an XML file. To see an example of the XML document that represents an activity type, export a Policy Type object and view the saved XML file.

To import the exported Policy Type objects and containers

  1. In the Active Roles console tree, under Configuration/Server Configuration/Policy Types, right-click the Policy Type container in which you want to import the exported Policy Type objects and containers.
  2. Click Import Policy Types, and then open the XML file you want to import.

This will create new Policy Type objects and containers in the selected container. In addition, new Script Modules will be created in the Configuration/Script Modules container and associated with the newly created Policy Type objects.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen