Chat now with support
Chat with Support

Active Roles 7.5 - 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
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 MFA Appendix H: Active Roles integration with Okta MFA

Scenario: Automatically moving users between groups

This scenario removes a user from the Seattle group and adds the user to the Atlanta group when the user relocates to Atlanta from Seattle.

Suppose user accounts of employees working in Seattle belong to the Seattle group, and user accounts of those working in Atlanta belong to the Atlanta group. The group to which the user belongs is defined by the city attribute: employees working in Seattle have user accounts with the value Seattle for the City attribute. For those working in Atlanta, the value is Atlanta.

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

  1. Create the Seattle and Atlanta groups.
  2. Configure membership rules to add users with a city value of Seattle to the Seattle group, and those with Atlanta to the Atlanta group.

As a result, only user accounts that currently have a city value of Seattle belong to the Seattle group. Thus, when an employee leaves Seattle for Atlanta, an administrator changes the City attribute from Seattle to Atlanta, and the user automatically moves to the Atlanta group because of the membership rule. Conversely, when an employee leaves Atlanta for Seattle, the administrator changes the city attribute from Atlanta to Seattle, and the user automatically transfers to the Seattle group.

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

Step 1: Creating the groups

To create the Seattle group, in the console tree, right-click the container where you want to add the group, and select New | Group. Follow the instructions in the New Object – Group wizard. In the Group name box, type Seattle.

To create the Atlanta group, in the console tree, right-click the container where you want to add the group, and select New | Group. Follow the instructions in the New Object – Group wizard. In the Group name box, type Atlanta.

Step 2: Configuring the membership rules

In this scenario, employees working in Seattle have user accounts with a value of Seattle for the City attribute. Those working in Atlanta have a value of Atlanta.

First, configure the membership rule for the Seattle group. Right-click the group and click Convert to Dynamic Group. In the confirmation message box, click Yes.

On the first page of the New Membership Rule wizard, click Include by Query, and then click Next.

On the second page, click Add to display the Create Membership Rules dialog box. Then, follow these steps to configure the membership rule:

  1. In the Find list, click Users.
  2. Click Browse and select the domain, OU, or Managed Unit that holds user accounts of the employees.
  3. Click the Advanced tab.
  4. Click Field, click City, and then click OK in the Select Object Property dialog box.
  5. In the Condition list, click Is (exactly).
  6. In the Value box, type Seattle.
  7. Click Add, and then click the Add Rule button.

When you are done, click Finish in the New Membership Rule wizard.

Repeat the same procedure for the Atlanta group, but type Atlanta in the Value box when configuring the membership rule.

Active Roles Reporting

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating