Chat now with support
Chat mit 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

Configuring a custom generation rule

Configuring a custom generation rule

To configure a custom rule, click Other combination of user properties, and then click the Configure button. This displays the Configure Value dialog box, discussed earlier in this chapter (see How to configure a Property Generation and Validation policy). You can use that dialog box to set up a value for the ‘Alias’ must be condition, the same way you configure a Property Generation and Validation policy.

To start configuring a value, click Add in the Configure Value dialog box. This displays the Add Entry window.

A value is a concatenation of one or more entries. In the Add Entry window, you can select the type of the entry to add, and then configure the entry. The following table summarizes the available types of entries.

Table 20: Available entries

Type of entry

Description

Text

Adds a text string to the value.

Uniqueness Number

Adds a numeric value the policy will increment in the event of an alias naming conflict.

User Property

Adds a selected property (or a part of a property) of the user account to which the policy will assign the alias.

Parent OU Property

Adds a selected property (or a part of a property) of an organizational unit in the hierarchy of containers above the user account to which the policy will assign the alias.

Parent Domain Property

Adds a selected property (or a part of a property) of the domain of the user account to which the policy will assign the alias.

Instructions on how to configure an entry depend on the type of the entry. For each type of an entry, you can find the instructions earlier in this chapter:

When you are done configuring a value, click OK to close the Configure Value dialog box. This will add the value to the policy rule. If necessary, you can modify the value by clicking the Configure button and then managing the list of entries in the Configure Value dialog box.

When you are done configuring the policy rule, click Next on the E-mail Alias Generation Rule page and follow the instructions in the wizard to create the Policy Object.

Steps for configuring an E-mail Alias Generation policy

To configure an E-mail Alias Generation policy

  1. On the Policy to Configure page, select E-mail Alias Generation, and then click Next.
  2. On the E-mail Alias Generation Rule page, do the following:
    • Select one of the pre-configured generation rules, or create a custom alias-generation rule. To create a custom rule, click Other combination of user properties, click Configure, and complete the Configure Value dialog box by using the procedure outlined later in this topic.
    • If you want the e-mail alias to be allowed for manual edit, select Allow manual edits of e-mail alias. Then, do one the following:
      • Click Always to authorize the operator who creates or updates the user account to modify the e-mail alias.
      • Click Only if a unique alias cannot be generated by this policy to allow manual changes only in the situation where a policy-generated alias is already assigned to a different user account.

    Click Next.

  3. 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.
  4. Click Next, and then click Finish.

To complete the Configure Value dialog box

  1. Click Add.
  2. Configure an entry to include in the value (for instructions, see Steps for configuring entries).
  3. In the Configure Value dialog box, add more entries, delete or edit existing ones, and then click OK.

Scenario: Generating e-mail alias based on user names

The policy described in this scenario generates the e-mail alias in accordance with this rule: user first name, optionally followed by a three-digit uniqueness number, followed by a period, followed by the user last name. Examples of aliases generated by this rule are as follows:

  • John.Smith
  • John001.Smith
  • John002.Smith

The policy generates the alias John001.Smith for the user John Smith if the alias John.Smith is in use. If both John.Smith and John001.Smith are in use, the policy generates the alias John002.Smith, and so on.

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

  1. Create and 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 assigning an e-mail alias to a user account in the container you selected in Step 2, the Active Roles user interfaces provide a Generate button to create the alias in accordance with the policy rule. In the event of an alias naming conflict, clicking the Generate button causes the policy to add a uniqueness number to the alias.

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 E-mail Alias Generation on the Select Policy Type page of the wizard. Then, click Next.

On the E-mail Alias Generation Rule page, click Other combination of user properties, and then click Configure.

Complete the Configure Value dialog box as follows:

  1. Click Add.
  2. Configure the entry to include the user first name:
    1. Under Entry type, click User Property.
    2. Under Entry properties, click Select.
    3. In the Select Object Property window, click First Name in the Object property list, and then click OK.
    4. Click OK.
  3. Click Add.
  4. Configure the entry to optionally include a uniqueness number:
    1. Under Entry type, click Uniqueness Number.
    2. Under Entry properties, set the entry options:
      • Click Add if the property value is in use.
      • Select the Fixed-length number, with leading zeroes check box.
      • In the box next to Length of the number, in digits, type 3.
    3. Click OK.
  5. Click Add.
  6. Configure the entry to include the period character:
    1. In Text value under Entry properties, type the period character.
    2. Click OK.
  7. Click Add.
  8. Configure the entry to include the user last name:
    1. Under Entry type, click User Property.
    2. Under Entry properties, click Select.
    3. In the Select Object Property window, click Last Name in the Object property list, and then click OK.
    4. Click OK.

After you complete these steps, the list of entries in the Configure Value dialog box should look like the following figure.

  1. Click OK to close the Configure Value dialog box. Then, click Next and follow the instructions in the wizard to create the Policy Object.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen