Chat now with support
Chat with Support

Active Roles 7.2.1 - Administrator 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 Home Folder AutoProvisioning Script Execution User Account Deprovisioning 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 Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Configuring replication Using AlwaysOn Availability Groups Using database mirroring 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
Using regular expressions Administrative Template Communication ports

Deploying an Access Rule (demonstration steps)

Role-based Administration > Windows claims-based Access Rules > Deploying an Access Rule (demonstration steps)

This section demonstrates how to implement a security scenario where each delegated administrator is restricted to managing users from a single department. The scenario is implemented by using an Access Rule that enables a delegated administrator to access only those objects whose Department property is identical with the Department claim of that delegated administrator.

Step 1. Prerequisites

In this section, we assume that you already have the following prerequisites:

  • An Active Directory domain, with at least one domain controller running Windows Server 2012 (or a later version of the Windows Server operating system).
  • The Active Roles Administration Service and MMC Interface (console) of the latest version installed on a member server in your Active Directory domain, with the server running Windows Server 2012 (or a later version of the Windows Server operating system).
  • Your Active Directory domain is registered with Active Roles as a managed domain.

Step 2. Enable claim support

Configure Group Policy to enable domain controllers to issue claims:

  1. On a domain controller running Windows Server 2012 or later, open the Group Policy Management console.

    To open the console, press Windows logo key+R to open the Run dialog box, type gpmc.msc, and click OK.

  1. In the console tree, select the Domain Controllers OU under your domain.
  2. In the details pane, right-click Default Domain Controllers Policy, and then click Edit.
  3. Perform the following steps in the Group Policy Management Editor console that appears:
    1. In the console tree, select Computer Configuration | Policies | Administrative Templates | System | KDC.
    2. In the details pane, double-click KDC support for claims, compound authentication and Kerberos armoring.
    3. In the KDC support for claims, compound authentication and Kerberos armoring dialog box, click Enabled and select Supported from the Options drop-down list. When finished, click OK to close the dialog box.
  4. Close Group Policy Management Editor.
  5. Close Group Policy Management.
  6. Open a command prompt and enter the following command: gpupdate /force.

Configure Group Policy to enable the Active Roles Administration Service to retrieve claims for clients by using Kerberos protocol transition:

  1. On the server running the Active Roles Administration Service, open the Local Group Policy Editor console.

    To open the console, press Windows logo key+R to open the Run dialog box, type gpedit.msc, and click OK.

  1. In the console tree, select Computer Configuration | Administrative Templates | System | Kerberos.
  2. In the details pane, double-click Kerberos client support for claims, compound authentication and Kerberos armoring.
  3. In the Kerberos client support for claims, compound authentication and Kerberos armoring dialog box, click Enabled, and then click OK.
  4. Restart the computer to apply the new setting to the Active Roles Administration Service. (Restarting only the Administration Service may not suffice.)

Add the Service Principal Names (SPNs) of the Active Roles Administration Service to the service account, to enable support for Kerberos authentication. Enter the following commands at a command prompt, where <FQDN> stands for the fully qualified domain name of the computer running the Administration Service; <name> stands for the name of that computer; and <ServiceAccountName> stands for the name of the service account (domain user account under which the Administration Service runs):

  1. setspn -s aradminsvc/<FQDN> <ServiceAccountName>

    For example, setspn -s aradminsvc/arsrv.domain.com domain\arsvcacct 

  1. setspn -s aradminsvc/<name> <ServiceAccountName>

    For example, setspn -s aradminsvc/arsrv domain\arsvcacct

Step 3. Create Claim Type

Create a Claim Type object for your domain controller to issue user claims sourced from the Department attribute. Log on as an Active Roles Admin and perform the following steps in the Active Roles console. (Assuming the default configuration, you should log on with a domain user account that is a member of the Administrators local group of the member server running the Active Roles Administration Service.)

  1. In the console tree, expand the Active Directory node, right-click the Claim Types container, and select New | Claim Type.
  2. On the Source Attribute page, scroll down the list of attributes, and click Department.
  3. Click Next and then click Finish.
Related Documents