Chat now with support
Chat with Support

Active Roles 7.2 - 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 Home Folder AutoProvisioning Script Execution User Account Deprovisioning 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 Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Configuring replication Using AlwaysOn Availability Groups Using database mirroring 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
Using regular expressions Administrative Template Communication ports

Steps for configuring a Script Execution policy

To configure a Script Execution policy

  1. On the Policy to Configure page, select Script Execution, and then click Next.
  2. On the Script Module page, do one of the following:
    • To use an existing script module, click Select a script module, and select the script module in the box beneath this option.
    • To create a new script module, click Create a new script module, and click Next. Then, specify a name for the script module, and click Next. Then, select the event handlers you want the script module to include.
  3. Click Next.
  4. On the Policy Parameters page, do the following:
    1. If necessary, from the Function to declare parameters list, choose the function that defines the parameters specific to this policy.

      The list contains the names of all script functions found in the selected Script Module. The policy has the parameters that are defined by the function specified in the Function to declare parameters box. Normally, this is a function named onInit.

    1. Under Parameter values, view or change the values of the policy parameters. To change the value of a parameter, select the name of the parameter and click Edit.

      Clicking Edit displays a page where you can add, remove or select a value or values for the selected parameter. For each parameter, the function that is used to declare parameters defines the name of the parameter and other characteristics, such as a description, a list of possible values, the default value, and whether a value is required. If a list of possible values is defined, then you can only select values from that list.

  5. On the Enforce Policy page, you can specify objects to which this Policy Object is to be applied:
    • Click Add, and use the Select Objects dialog box to locate and select the objects you want.
  6. Click Next, and then click Finish.

To create a script module

  1. In the console tree, under Configuration | Script Modules, locate and select the folder in which you want to add the script module.

    You can create a new folder as follows: Right-click Script Modules and select New | Scripts Container. Similarly, you can create a sub-folder in a folder: Right-click the folder and select New | Scripts Container.

  1. Right-click the folder and select New | Script Module.
  2. Specify the name and language of the module to create. Then, click Next.
  3. In Select a script module type, click the type of the module to create. Then, click Next.
  4. If you selected the Policy script type for the module, select the event handlers you want the module to include, and then click Next.
  5. Click Finish.

To edit a script module

  1. In the console tree, expand Configuration | Script Modules.
  2. Under Script Modules, click the folder that contains the script module you want to edit.
  3. In the details pane, right-click the script module, and then click Edit Script.
  4. Use the details pane to make changes to the script.
  5. Right-click the script module in the console tree, and do one of the following:
    • To commit the changes you have made, click Save Script on Server.
    • To quit the script editor without saving your changes, click Discard Changes.

To import a script module

  1. In the console tree, under Configuration | Script Modules, locate and select the folder in which you want to add the script module.

    You can create a new folder as follows: Right-click Script Modules and select New | Scripts Container. Similarly, you can create a sub-folder in a folder: Right-click the folder and select New | Scripts Container.

  1. Right-click the folder, and click Import.
  2. Locate and select the file containing the script to import, and click Open.

To export a script module

  1. In the console tree, expand Configuration | Script Modules.
  2. Under Script Modules, select the folder that contains the script module you want to export.
  3. In the details pane, right-click the script module, and select All Tasks | Export.
  4. Specify the file to which you want to save the script, and then click Save.

Scenario: Restricting group scope

This scenario describes how to configure a policy that prevents creation of universal groups. With this policy, the Active Roles console or Web Interface does not allow an administrator to create a new universal group or convert an existing group to a universal group.

To implement this scenario, you must perform the following actions:

  1. Prepare the script that implements this scenario.
  2. Create and configure the Policy Object to run that script.
  3. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, the Active Roles console or Web Interface cannot be used to set the universal group scope option when creating a new group or changing an existing group in the container you selected in Step 3. For example, if you choose the Universal option under Group scope and then click Next in the New Object - Group wizard, the Active Roles console presents you with an error message stating that creation of universal groups is not allowed.

The following sections elaborate on the steps to implement this scenario.

Step 1: Preparing the script module

Step 1: Preparing the script module

The script used in this scenario is installed with the Active Roles SDK. By default, the path and name of the script file is as follows:
%ProgramFiles%\One Identity\Active Roles\Active Roles\SDK\Samples\RestrictGroupScope\RestrictGroupScope.ps1

The script receives control upon a request to check the property values submitted to the Administration Service, and analyzes the value of the groupType attribute to determine if the universal group scope option is attempted. If the script detects that the assumed groupType value would cause a group to be configured as a universal group, it raises a policy violation event in the Administration Service. As a result, the application that initiated the request (such as the Active Roles console or Web Interface) displays an error message provided by the script. For more information, see the “Restricting the Scope of Groups” topic in the Active Roles SDK documentation.

To import the script, right-click the Script Modules container in the Active Roles console, and click Import. Then, select and open the RestrictGroupScope.ps1 file.

Step 2: Creating and configuring the Policy Object

Rule-based AutoProvisioning and Deprovisioning > Policy configuration tasks > Script Execution > Step 2: Creating and configuring the Policy Object
Step 2: Creating and configuring the Policy Object

You can create and configure the Policy Object you need by using the New Provisioning Policy Object wizard. For information about the wizard, see Creating a Policy Object in the Policy Object management tasks section earlier in this chapter.

To configure the policy, click Script Execution on the Policy to Configure page of the wizard. Then, click Next.

On the Script Module page, click Select a script module, and select RestrictGroupScope from the list of script modules, as shown in the following figure.

Figure 66: Script Module: Creating/configuring policy object

Click Next and follow the instructions in the wizard to create the Policy Object.

Related Documents