Chatee ahora con Soporte
Chat con el soporte

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

Apply an Access Rule to Access Template links

Access Rules are intended to be applied to Access Template links. A single Access Rule or no Access Rule can be applied to a given link. By default, no Access Rule is applied, which configures an unconditional link. By applying an Access Rule, you create a conditional link that has an effect only if the Access Rule’s conditional expression evaluates to True during permission check.

To apply an Access Rule

  1. In a list of Access Template links, double-click the Access Template link to which you want to apply the Access Rule.

    You can select Access Template links from various lists provided be the Active Roles console. Thus, you can use the Delegate Control command on a container object to display a list of all Access Template links that determine the permission settings for that container. The Links command on an Access Template displays all links of that Access Template. The Active Roles Security tab in the advanced details pane lists the Access Template links that determine the security settings for the object selected in the Active Roles console.

  1. In the Properties dialog box that appears, click the Access Rule tab.
  2. Click the Change button, and then select the Access Rule you want to apply.

From the Access Rule tab, you can also perform the following tasks:

  • Choose a different Access Rule for the selected Access Template link. Click the Change button and choose the Access Rule you want.
  • View or change the Access Rule applied to the selected Access Template link. Click the Properties button and then go to the Conditions page to review or modify the Access Rule’s conditional expression.
  • Remove the Access Rule from the selected Access Template link. Click the Clear button to remove the Access Rule.

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 2016 (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 2016 (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 2016 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

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación