Chat now with support
Chat with Support

Active Roles 8.0 LTS - 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 Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users 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 Microsoft 365 Groups Managing Azure Security Groups Managing cloud-only distribution 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 cloud-only shared 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: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta Active Roles Language Pack

Steps for connecting to the Administration Service

When you start the Active Roles console, it automatically selects the appropriate Administration Service, and establishes a connection to that Service. However, you can connect to a specific Administration Service at any time.

To select the Administration Service to connect to

  1. In the console tree, right-click Active Roles, and then click Connect.
  2. In the Service box, type or select the name of the computer running the Administration Service to connect to, and then click the Connect button.

NOTE:

  • If you do not see the Administration Service you want in the Service list, click the Select button next to the Service box. This displays a list of the Administration Services that are available in the specified forest. You can choose a different forest by clicking Change. To add a certain Service to the Service list, click that Service in the list of available Administration Services, and then click OK.
  • If you need to establish a connection under a user account other than your logon account, click Options to display the Connect as area, and then click The following user and specify the user logon name and password of the account to be used for connection. By selecting the Remember password check box, you can have the console automatically use the specified user name and password in the future connection sessions. Otherwise, on a subsequent start, the console will prompt you for a password.

Adding and removing managed domains

Active Directory domains registered with Active Roles are referred to as managed domains. Each Administration Service maintains a list of managed domains, and stores this list in the Administration Database as part of the service configuration.

In the Active Roles console, the Add Managed Domain wizard is used to register domains for management. You can access the wizard as follows: Click the console tree root; then, in the details pane, in the Domains area, click Add Domain.

The Add Managed Domain wizard prompts you for the following information:

  • The name of the domain you want to register.
  • The credentials that Active Roles will use to access the domain.

You have the option to use the default credentials (the service account of the Administration Service) or enter the user name and password of a different account (override account). In both cases, the account must have adequate rights in the managed domain. For more information, refer to the “Access to Managed Domains” section in the Active Roles Quick Start Guide.

If you choose the option to access the managed domain using the service account information, consider the following. This option applies to all Administration Services in your environment. Each Administration Service in your environment will use its own service account to access the domain. Since different service accounts may have different levels of access to the domain, Active Roles may have different access rights to the domain, depending on which Administration Service is being used to manage the domain. The result is that the behavior of Active Roles may vary when you switch to a different Administration Service.

After you add a managed domain, the Administration Service retrieves the domain information, such as the Active Directory schema and the hierarchy of containers. This process is referred to as loading domain information.

It may take a few minutes for the Administration Service to load the domain information. Once this process is completed, the domain is available for management. Select the Active Directory item in the console tree and press F5 to refresh the details pane and display the new domain. To start managing the domain, select it in the details pane and press ENTER; or expand the domain item in the console tree.

It is possible to remove a domain from the list of managed domains. Once removed, the domain and all directory objects contained in the domain can no longer be managed with Active Roles. To remove a managed domain, select the console tree root and click Go to Managed Domains in the details pane, in the Domains area. This causes the details pane to display a list of managed domains. In the list, right-click the domain you want to remove, and click Delete.

Steps for adding or removing a managed domain

The operation of adding a managed domain results in the creation of an object that holds the registration information about the domain. For this reason, it is also referred to as registering a domain with Active Roles.

To add a managed domain

  1. In the console tree, expand Configuration | Server Configuration.
  2. Under Server Configuration, right-click Managed Domains, and select New | Managed Domain to start the Add Managed Domain wizard.
  3. On the Welcome page of the wizard, click Next.
  4. On the Domain Selection page, do one of the following, and then click Next.
    • Type the name of the domain you want to add.
    • Click Browse, and select the domain from the list.
  5. On the Active Roles Credentials page, click one of these options that determine the logon information that Active Roles will use to access the domain:
    • The service account information the Administration Service uses to log on
    • The Windows user account information specified below

If you choose the second option, type the user name and password of the user account you want Active Roles to use when accessing the domain.

  1. Click Next, and then click Finish.

To remove a managed domain

  1. In the console tree, expand Configuration | Server Configuration.
  2. Under Server Configuration, click Managed Domains.
  3. In the details pane, right-click the domain you want to remove, and then click Delete.

NOTE:

  • You can use the Properties command on an object held in the Managed Domains container to view or modify the registration information for the respective managed domain. For example, it is possible to change the logon information that is used to access the domain: on the General tab in the Properties dialog box, choose the appropriate option and click Apply. You can choose one of the two options that are listed in Step 5 of the procedure above.
  • The Managed Domains container holds the registration objects for all domains that are registered with Active Roles. You can un-register domains by deleting objects from that container.
  • By default, no domains are registered with Active Roles. When you register a domain, the domain registration is saved as part of the Active Roles configuration.

Using unmanaged domains

After you’ve registered an Active Directory domain with Active Roles, you have the option to use the domain as an unmanaged domain. An unmanaged domain is basically a domain that is registered with Active Roles for read-only access. The use of the unmanaged domain option allows you to reduce licensing costs since the user count that corresponds to the unmanaged domains is not added to product usage statistics (see Evaluating product usage).

Unmanaged domains are instrumental in the following scenarios:

  • Group membership management  When used to add members to a group, by selecting the new members from a list of objects, Active Roles requires the domain that holds the objects to be registered. If you only use Active Roles for selecting member objects when managing group membership, you can configure the domain that holds the member objects as an unmanaged domain.
  • Exchange resource forest  When used to create Exchange mailboxes in a forest that is different from the forest that holds the accounts of the mailbox users, Active Roles requires the domain of the mailbox users (account domain) to be registered. If you do not use Active Roles for user management in the account domain, you can make that domain an unmanaged domain.

As applied to a registered unmanaged domain, the features and functions of Active Roles are limited to those that do not require write access to the objects held in that domain (including write access to the object data that is stored by Active Roles as virtual attributes). Thus, you can use Active Roles to:

  • Search for, list and select objects from unmanaged domains
  • Populate groups in regular managed domains with objects from unmanaged domains
  • Retrieve and view properties of objects held in unmanaged domains
  • Assign users or groups from unmanaged domains to the role of manager, primary owner, or secondary owner for objects held in regular managed domains
  • Delegate management tasks and approval tasks to users or groups held in unmanaged domains
  • Run Active Roles policies against objects held in unmanaged domains, provided that the policies require only read access to those objects
  • Provision users from unmanaged domains with linked Exchange mailboxes held in a separate managed forest
  • Populate Managed Units with objects from unmanaged domains

Since Active Roles has read-only access to unmanaged domains, it cannot:

  • Create, move, or delete objects in unmanaged domains
  • Change any properties of objects held in unmanaged domains
  • Run any group membership related policies against the groups in unmanaged domains, including the Group Family and Dynamic Group policies
  • Run any auto-provisioning or deprovisioning policies against the users or groups held in unmanaged domains
  • Run any workflow that makes changes to objects in unmanaged domains
  • Restore objects from Active Directory Recycle Bin in unmanaged domains
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating