Chat now with support
Chat with Support

Active Roles 7.4.1 - 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 License Management Office 365 Roles Management 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_Overview
Config ARS to Manage Hybrid AD Objects Managing Hybrid AD Users Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Azure O365 or Unified Groups
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 delegation for Federated Authentication

Changing the service account

With the Windows authentication option selected for database connection, the Administration Service uses its service account to authenticate with SQL Server. Additionally, if the Administration Service’s database server holds the Publisher role, and has a Subscriber with Windows authentication, the service account requires the appropriate permissions on the Subscriber SQL Server. For details, see the “SQL Server permissions” section in the Active Roles Quick Start Guide.

Given this role of the service account, you may need to specify a different service account with sufficient SQL Server permissions. Also, you may need to change the service account’s password. You can view or change the service account by using Active Roles Configuration Center as follows.

  1. Start Configuration Center on the computer running the Administration Service, or connect Configuration Center to that computer.

You can start Configuration Center by selecting Active Roles 7.4 Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For detailed instructions, see “Running Configuration Center” in the Active Roles Administrator Guide.

  1. On the Dashboard page in the Configuration Center main window, click Manage Settings in the Administration Service area.
  2. On the Administration Service page that opens, click Change in the Service account area.
  3. On the Change Service Account page that appears, type the logon name and password of the service account, and then click Change.

Changing the SQL Server Agent logon account

If the Publisher has a Subscriber that uses Windows authentication, it is required that the SQL Server Agent logon account on the Publisher SQL Server have appropriate access permissions on the Subscriber SQL Server. For details, see the “SQL Server permissions” section in the Active Roles Quick Start Guide.

Given these requirements of the SQL Server Agent logon account, you may encounter a situation where you need to specify a different logon account with sufficient access permissions. You may also need to change password for the logon account. This section provides instructions on how to change the SQL Server Agent logon account.

You can specify the name and password of the SQL Server Agent logon account by using SQL Server Configuration Manager:

  1. On the computer running the Publisher SQL Server, open SQL Server Configuration Manager.
  2. In the console tree, select SQL Server Services.
  3. In the details pane, right-click the SQL Server Agent to modify, and then click Properties.
  4. On the Log On tab, click This account, and specify the account name and password.
  5. Click OK.
  6. For the changes to take effect, click Yes in the confirmation message box.

Modifying Replication Agent credentials

This section provides information on how to repair Active Roles replication if it fails due to insufficient permissions of Replication Agents. The credentials used by Replication Agents to access a given SQL Server depend on authentication mode of the Administration Service connection to that SQL Server:

  • Windows authentication In this mode, Replication Agents use the credentials of the SQL Server Agent service running on the Publisher SQL Server computer
  • SQL Server authentication In this mode, Replication Agents use the credentials of the SQL Server login specified for the Administration Service connection to SQL Server

The following sub-sections elaborate on each of these two options.

Windows authentication

If the Administration Service uses Windows authentication, Replication Agents connect to SQL Server in the security context of the SQL Server Agent service. Therefore, the SQL Server Agent logon account must have sufficient permissions for replication to work properly (see the “SQL Server permissions” section in the Active Roles Quick Start Guide.

If the SQL Server Agent logon account does not have the appropriate permissions, is deleted, or has the password changed, Active Roles replication fails. To resolve this problem, give the required permissions to the logon account, or configure the SQL Server Agent service to log on with a different account that has the appropriate permissions. For instructions on how to configure the SQL Server Agent service to log on with a given account, see Changing the SQL Server Agent logon account earlier in this document.

You can use the following instructions to verify that the Replication Agents are configured properly. The instructions vary depending on whether the SQL Server holds the Publisher or Subscriber role. In both cases, you should connect to the Publisher SQL Server using SQL Server Management Studio.

Replication Agent connection to Publisher

If the Administration Service connects to the Publisher SQL Server using Windows authentication, follow these steps to verify that the Replication Agents are configured properly:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.
  2. In the Object Browser, under the Publisher SQL Server, right-click the Replication folder, and then click Distributor Properties.
  3. In the left pane of the Distributor Properties window, click Publishers.
  4. In the Publishers list, select the entry representing the Publisher SQL Server, and click the button in that entry to display the Publisher Properties dialog box.
  5. In the Publisher Properties dialog box, under Agent Connection to the Publisher, verify that the Agent Connection Mode property is set to Impersonate the agent process account.

Replication Agent connection to Subscriber

If the Administration Service connects to the Subscriber SQL Server using Windows authentication, follow these steps to verify that the Replication Agents are configured properly:

  1. With SQL Server Management Studio, connect to the Publisher SQL Server.

    NOTE: You must have Management Studio connected to the Publisher SQL Server, regardless of whether you are managing Replication Agents for the Publisher or for a Subscriber.

  1. In the Object Browser, under the Publisher SQL Server, expand Replication | Local Publications | AelitaReplica.
  2. In the list under AelitaReplica, right-click the entry corresponding to the Subscriber SQL Server and click Properties.
  3. In the Subscription Properties window, in the Security section, expand the Subscriber connection entry.
  4. Verify that the Subscriber connection property is set to Impersonate agent process account (Windows Authentication).
Related Documents