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

Replication is already configured

This section outlines the instructions on how to turn off replication of Management History data in case that Active Roles replication is already configured as described in the Configuring replication section later in this document. You need to first delete all Subscribers for Management History data, and then demote the Publisher for Management History data. This only stops replication of Management History data, leaving the other replication functions intact.

To turn off replication of Management History data

  1. With the Active Roles console, connect to the Administration Service whose SQL Server holds the Publisher role.
  2. In the console tree, expand Configuration | Server Configuration, and select the Management History Databases container.
  3. Use the Delete command on each of the Subscriber databases to delete all Subscribers in the Management History Databases container.
  4. Right-click the Publisher database, and click Demote.
  5. Wait while the console completes the Demote operation.

Re-configuring replication of Management History data

With replication of Management History data turned off, it is still possible to have multiple Administration Services maintain the same Change History log by configuring them to use the same database. Note that the Administration Service version 6.x allows you to install multiple Services with the option to connect to a single configuration database. Thus, you can install the first Service in your environment, having the Setup program create a database. Then, you can install one more Service, having the Setup program configure the new Service to use the same database as the existing Service.

However, if different Administration Services in your environment use different database servers, you may need to re-configure replication of Management History data in order to take full advantage of the Management History feature. You can do so by managing objects in the Management History Databases container as follows.

To re-configure replication of Management History data

  1. With the Active Roles console, connect to the Administration Service whose SQL Server holds the Publisher role for configuration data.
  2. In the console tree, expand Configuration | Server Configuration, and select the Management History Databases container.
  3. In the details pane, right-click the database, and click Promote.
  4. Wait while the console performs the Promote operation.
  5. Use the Add Replication Partner command on the Publisher database in the Management History Databases container to add Subscribers for Management History data.

The Add Replication Partner command starts the wizard that is similar to that discussed in the Adding members to a replication group section later in this document. The only difference is that the list of Administration Services whose database servers can be designated as Subscribers for Management History data is limited to those Services that share the configuration data hosted on the Publisher you have selected.

Centralized Management History storage

With the default replication settings in Active Roles, the Management History data is synchronized between replication partners, along with the Configuration data. Given a large volume of Management History data, this behavior may result in high network traffic and may cause performance degradation of Active Roles in certain scenarios, such as when adding a new partner to the Active Roles replication group. Here you can find instruction on how to eliminate replication of Management History data by implementing a common storage of that data for all replication partners.

Synchronization of the Management History data can be removed from the Active Roles replication process by implementing a common storage of that data for all replication partners. The common storage ensures the consolidation of the portions of Management History data that are generated by different Administration Services, while eliminating the need to synchronize that data between multiple storages.

By default, Active Roles allows you to implement a centralized, common storage for the Management History data. In this way, all the Administration Services that share common configuration use the same Management History storage - the Management History database you created.

Importing data to the new Management History database

You may need to populate the newly created Management History database with your existing Management History data, so that the data remains available to the Active Roles user interfaces after you have configured the Administration Service to use the new Management History database. You can do this by using Active Roles Configuration Center on the computer running the Administration Service.

IMPORTANT: The reports produced by the Change History or User Activity command include information only about the changes made using a certain group of Administration Services that share a common database from the connected management history database. If the Change History data is not imported from the previously available database, the data is not displayed in the new Management History database. For more information on the implications of not importing the Change History data from the available database, see Impact on management history data in the Active Roles What's New guide.

To import Management History data

  1. In the Configuration Center main window, under Administration Service, click Manage Settings.

    Start the Configuration Center by selecting Active Roles7.5 Configuration Center on the Apps page or Start menu, depending on the version of your Windows operating system.

  2. On the Administration Service page, click Import Management History to open the Import Management History wizard.

  3. On the Source database page, specify the database from which you want to import the management history data (source database):

    1. Database Type: Select the required database type from the drop-down (on premises or Azure SQL).

    2. Database Server name: Enter the name of the SQL Server instance that hosts the source database.

    3. Database: Enter the name of the source database.

  4. Under Connect using, select the authentication option:

    • If your Windows logon account has sufficient rights to write data to the destination database, click Windows authentication.

    • If you have a SQL Server login with sufficient rights, click SQL Server authentication and enter the login name and password.

    • If you have an Azure AD login with sufficient rights, click Azure Active Directory authentication and enter the login name and password.

    NOTE: Azure databases can be connected using SQL Server authentication and Azure AD authentication. Windows authentication is applicable only for on-premises databases.

    NOTE: Azure AD authentication currently does not support Multi-Factor Authentication (MFA).

  5. Click Next.

    The Destination database page identifies the database of the Administration Service to which you are going to import data (destination database), and allows you to select the authentication option.

  6. Under Connect using, select the authentication option:

    • If your Windows logon account has sufficient rights to write data to the destination database, click Windows authentication.

    • If you have a SQL Server login with sufficient rights, click SQL Server authentication and enter the login name and password.

    • If you have an Azure AD login with sufficient rights, click Azure Active Directory authentication and enter the login name and password.

    NOTE: Azure databases can be connected using SQL Server authentication and Azure AD authentication. Windows authentication is applicable only for on-premises databases.

    NOTE: Azure AD authentication currently does not support Multi-Factor Authentication (MFA).

  7. Click Next.

  8. On the Records to Import page, specify whether you want to import all data records or only a certain range of the data records.

    NOTE: The data for unfinished temporal group membership is imported when the management history data is imported for a selected date range.

    You can choose not to import all the data records as importing a large volume of data can take hours. Later, you can import additional data by choosing a different range of data records. During subsequent import sessions, the wizard only imports the data records that were not imported earlier.

  9. Click Next and follow the instructions in the wizard to complete the import operation.

The Import Management History wizard merges the Management History data found in an existing Active Roles database with the data stored in the Management History database. The wizard only adds new data, keeping intact any data that already exists in the Management History database. You may import Management History data at any convenient time after you have configured the Administration Service to use the new Management History database, without being afraid of losing any data.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating