Chatta subito con l'assistenza
Chat con il supporto

Active Roles 8.2 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Configuring rule-based autoprovisioning and deprovisioning
Configuring Provisioning Policy Objects
User Logon Name Generation E-mail Alias Generation Exchange Mailbox AutoProvisioning Group Membership AutoProvisioning Home Folder AutoProvisioning Property Generation and Validation Script Execution O365 and Azure Tenant Selection AutoProvisioning in SaaS products
Configuring Deprovisioning Policy Objects
User Account Deprovisioning Group Membership Removal User Account Relocation Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Permanent Deletion Office 365 Licenses Retention Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Script Execution Notification Distribution Report Distribution
Configuring entry types Configuring a Container Deletion Prevention policy Configuring picture management rules Managing Policy Objects Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Configuring policy extensions
Using rule-based and role-based tools for granular administration Workflows
About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow 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
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Azure tenant types and environment types supported by Active Roles Using Active Roles to manage Azure AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
Managing the configuration of Active Roles
Connecting to the Administration Service 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 Using regular expressions Administrative Template Configuring federated authentication Communication ports and URLs used by Active Roles Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Example: Using regular expressions to control telephone number format

This scenario describes how to configure a policy that forces the user telephone number to conform to the following format:

  • The first character must be +.

  • The second character(s) must be the country code. For example, 1 in the United States and Canada, and 61 in Australia.

  • Use spaces (instead of dashes or braces) to separate the area code.

  • Use spaces (instead of dashes) to separate the telephone number.

  • Optionally, use a lowercase x to indicate an extension.

  • Use spaces (instead of dashes or braces) to separate the area code.

  • Use spaces (instead of dashes) to separate the telephone number.

  • Optionally, use a lowercase x to indicate an extension.

The following table provides some examples to clarify how the phone number should look in accordance with these formatting requirements.

Table 6: Phone number format

Correct

Incorrect

Comment

+1 949 754 8515

949-754-8515

The incorrect entry does not begin with + and country code, and uses dashes instead of space.

+44 1628 606699 x1199

+44 1628 606699 X1199

The incorrect entry uses uppercase X.

As a result, when creating or modifying a user object in the container that you selected, Active Roles validates the telephone number against the defined format. If it does not conform to the defined format, the policy does not allow creating or editing the user object.

For the steps of creating this policy, see Creating and configuring a Property Generation and Validation Policy Object with a regular expression.

Creating and configuring a Property Generation and Validation Policy Object with a regular expression

You can create the Property Generation and Validation policy that is described in Example: Using regular expressions to control telephone number format with the New Provisioning Policy Object Wizard.

To create and configure a Property Generation and Validation Policy Object with a regular expression

  1. In the Console tree, navigate to Configuration > Policies > Administration.

  2. To open the New Provisioning Policy Object Wizard dialog, right-click Administration, then select New > Provisioning Policy.

  3. On the Name and Description page, provide a unique Name for the new Policy Object. Optionally, also provide a Description. To continue, click Next.

  4. Select the Property Generation and Validation policy type for configuration. Click Next.

    For more information, see Configuring a Property Generation and Validation policy.

  5. On the Controlled Property page, click Select.

  6. In the Select Object Type and Property dialog, from the Object type list, select User.

  7. In the Object property list, select Telephone number.

    Figure 36: Select Object Type and Property

  8. After you selected the Object type and Object property, to continue, click OK.

  9. After you validated on the Controlled Property page that you selected the correct Object type and Object property, click Next.

  10. On the Configure Policy Rule page, select the following:

    ‘Telephone Number’ must match regular expression <value>: This condition requires the telephone number to match a certain regular expression.

    Figure 37: Configure Policy Rule: Telephone Number must be specified and must be <value>

  11. Add the regular expressions to the policy.

    The following table briefly describes the elements that are used in the two above syntax. For more information about regular expressions, see Using regular expressions.

    Table 7: Regular expressions

    This Element

    Indicates

    ^

    The beginning of the input string to validate.

    \+

    The escape sequence to represent the plus (+) character.

    ([0-9]+ )+

    Concatenation of one or more substrings, with each substring consisting of one or more digit characters followed by a space character.

    [0-9]+

    One or more digit characters.

    x[0-9]+

    A lowercase x followed by one or more digit characters.

    $

    The end of the input string to validate.

    You will configure the policy to only allow the telephone numbers that match ^\+([0-9]+ )+[0-9]+$ (telephone numbers without extensions) or ^\+([0-9]+ )+x[0-9]+$ (telephone numbers that include extensions). Proceed with configuring the policy as follows:

    1. Click the <click to add value> link.

    2. In the Add Value dialog, enter ^\+([0-9]+ )+[0-9]+$

      To apply the value setting for the entry, click OK.

    3. Click the <click to add value> link.

    4. In the Add Value dialog, enter ^\+([0-9]+ )+x[0-9]+$.

      To apply the value setting for the entry, click OK.

  12. Click Next, then follow the instructions in the wizard to create (and optionally, immediately apply) the Policy Object.

  13. To apply the Policy Object:

    • Use the Enforce Policy page in the New Policy Object Wizard.

    • Alternatively, complete the New Policy Object Wizard, then use the Enforce Policy command on the domain, OU, or Managed Unit where you want to apply the policy.

    For more information on how to apply a Policy Object, see Linking Policy Objects to directory objects.

    TIP: When provisioning cloud-only Azure users or guest users, you can either select the respective object category (such as the Azure user or Azure guest user node) in this step, or the Azure tenant that contains the Azure objects.

Script Execution

Script execution policies help you to run supplementary PowerShell, or other script modules in Active Roles during or after performing certain administrative operations. When linking a custom script to an administrative operation via a Script Execution policy, the script will receive control in Active Roles either when the operation is requested or when it is completed.

Use Script Execution policies to set up custom scripts (residing in Script Modules in the Active Roles Console) to:

  • Trigger additional actions when performing directory object provisioning.

  • Regulate object data format and requirements (such as for generating user passwords).

  • Further automate administrative tasks.

NOTE: Policy Object settings that are specific to Azure cloud-only objects (such as cloud-only Azure users, guest users, or contacts) are available only if your Active Roles deployment is licensed for managing cloud-only Azure objects. Contact One Identity support for more information.

Also, Policy Objects that are specific to Azure cloud-only objects will work correctly only if an Azure tenant is already configured in the AD of the organization, and Active Roles is already set as a consented Azure application for that Azure tenant. For more information on these settings, see Configuring a new Azure tenant and consenting Active Roles as an Azure applicationConfiguring a new Azure tenant and consenting Active Roles as an Azure application in the Active Roles Administration Guide.

For more information about this policy, see Concept: Script Execution in the Active Roles Feature Guide.

Configuring a Script Execution policy

To configure a Script Execution policy via the Active RolesConsole (also known as the MMC interface), perform the following procedure.

IMPORTANT: You must select a script module during this procedure. You can choose to either configure a script module before performing these steps, or create an empty script module while configuring the Script Execution policy, then configure the script module later.

To configure a Script Execution policy

  1. In the Console tree, navigate to Configuration > Policies > Administration.

  2. To open the New Policy Object Wizard dialog, choose one of the following:

    1. To add a provisioning policy, right-click Administration, then select New > Provisioning Policy.

    2. To add a deprovisioning policy, right-click Administration, then select New > Deprovisioning Policy.

  3. On the Name and Description page, provide a unique Name for the new Policy Object. Optionally, also provide a Description. To continue, click Next.

  4. On the Policy to Configure page, select Script Execution, then click Next.

  5. On the Script Module page, do one of the following:

    • To create new script module, click Create a new script module, then click Next. Specify a name for the script module, and click Next, then select the event handlers for the script module.

    • To use an existing script module, click Select a script module, and select the script module from the list, then click Next.

  6. (Optional) If you selected an existing script module, on the Policy Parameters page, edit the policy parameters:

    1. In the Function to declare parameters drop-down, choose the function that defines the parameters for the policy.

      The list contains the names of all script functions found in the selected script module.

    2. To view and change the values of policy parameters, under Parameter values, select the name of the parameter and click Edit.

    3. On the Edit Parameter page, modify the value of the parameter.

      NOTE: A list of possible values might be predefined for the selected parameter. In such cases, you can only select values from this list.

  7. Click Next, then follow the instructions in the wizard to create (and optionally, immediately apply) the Policy Object.

  8. To apply the Policy Object:

    • Use the Enforce Policy page in the New Policy Object Wizard.

    • Alternatively, complete the New Policy Object Wizard, then use the Enforce Policy command on the domain, OU, or Managed Unit where you want to apply the policy.

    For more information on how to apply a Policy Object, see Linking Policy Objects to directory objects.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione