Chat now with support
Chat with Support

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

Scenario 1: Using mask to control phone number format

This scenario describes how to configure a policy that forces the user phone number to conform to the format (###) ###-##-##.

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

  1. Create and configure a Policy Object that defines the appropriate policy.
  2. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, when creating or modifying a user object in the container you selected in Step 2, Active Roles checks whether the phone number conforms to the stated format. If not, the policy disallows the creation or modification of the user object.

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

Step 1: Creating and configuring the Policy Object

Step 1: 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 Property Generation and Validation on the Policy to Configure page of the wizard. Then, click Next.

On the Controlled Property page, click Select. Then, in the Select Object Type and Property dialog box, select User from the Object type list, and click Telephone number in the Object property list, as shown in the following figure.

Figure 40: Select Object type and property

Click OK, and then click Next.

On the Configure Policy Rule page, in the upper box, select the following check boxes:

  • ‘Telephone Number’ must be specified. This makes the phone number a required property, that is, requires that a phone number be specified in every user account.
  • ‘Telephone Number’ must be <value>. This allows you configure a mask for the telephone number by adding the appropriate entry to the value for this condition.

At this stage, the Configure Policy Rules page looks like the following figure.

Figure 41: Configure policy rules

The next phase is to configure the value.

Click the link labeled <click to add value>. In the Add Value dialog box, click Configure. In the Configure Value dialog box, click Add. In the Add Entry window, under Entry type, click Mask.

Now you can use the Entry properties area in the Add Entry window to configure a mask.

The format consists of four groups of numerals divided by certain characters—space character, hyphens, and brackets. First, configure a mask that requires the first three characters to be numerals:

  • Select Exactly the specified number of characters.
  • In the Number of characters box, enter 3.
  • Under Allowed characters, select the Numerals check box.

The Add Entry window should look as shown in the following figure.

Figure 42: Add entry

Click OK to close the Add Entry window. Then, click OK to close the Configure Value dialog box. As a result, the Add Value dialog box looks as shown in the following figure.

Figure 43: Add value dialog box

Taking into consideration the mask you have configured, you can guess that the mask for the phone number format you need is as follows:

({3 required [0-9]}) {3 required [0-9]}-{2 required [0-9]}-{2 required [0-9]}

Type this mask in the ‘Telephone Number’ must be box in the Add Value dialog box. Pay attention to the round brackets enclosing the first three characters, a space character following the group in the round brackets, and two hyphen characters that separate the groups of characters.

Click OK to close the Add Value dialog box. Click Next and follow the instructions in the wizard to create the Policy Object.

Step 2: Applying the Policy Object

Step 2: Applying the Policy Object

You can apply the Policy Object by using the Enforce Policy page in the New Provisioning Policy Object wizard, or you can complete the wizard and 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 Applying Policy Objects and Managing policy scope earlier in this chapter.

Scenario 2: Using regular expressions to control phone number format

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

  • The first character must be “+” .
  • The second character(s) must be the country code .

    (This is 1 in the US and Canada, and 61 in Australia for example.)

  • Use spaces (instead of dashes or braces) to separate area code.
  • Use spaces (instead of dashes) to separate the phone 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 17: 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 the upper-case X.

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

  1. Configure the Policy Object that defines the appropriate policy.
  2. Apply the Policy Object to a domain, OU, or Managed Unit.

As a result, when creating or modifying a user object in the container you selected in Step 2, Active Roles checks whether the phone number conforms to the stated format. If not, the policy disallows the creation or modification of the user object.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating