Chatta subito con l'assistenza
Chat con il supporto

Active Roles 8.1.5 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Rule-based autoprovisioning and deprovisioning
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation 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
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow 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
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
Managing the configuration of Active Roles
Connecting to the Administration Service 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 Using regular expressions Administrative Template Configuring federated authentication Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Prerequisites for using Access Rules

Before you can use Access Rules, the following conditions must be fulfilled:

  • Claim support must be enabled in your Active Directory domain. For details, review the topic Enabling claim support.

  • For Access Rules to use device claims, Group Policy setting Computer Configuration > Policies > Administrative Templates > System > Kerberos > Support Compound Authentication with the Always option must be enabled on the client computers, in addition to the Kerberos client support for claims, compound authentication and Kerberos armoring setting (see Client computer).

  • The Active Roles Administration Service must be installed on a computer running Windows Server 2016 or a later version of the Windows Server operating system.

  • The Active Roles Administration Service that performs authorization using Access Rules must be installed in the Active Directory forest where the user account of the authorizing user is defined and in which the claim types used by the Access Rules are created. Active Roles does not support the use of Access Rules for cross-forest authorization.

  • Group Policy setting Computer Configuration > Policies > Administrative Templates > System > Kerberos > Kerberos client support for claims, compound authentication and Kerberos armoring must be enabled on the computer running the Administration Service.

  • The Administration Service must be configured to support Kerberos authentication.

Configuring the Administration Service to support Kerberos authentication

Access Rules require the Active Roles Administration Service to support Kerberos authentication. This is because Windows claims are delivered inside Kerberos tickets. To enable Kerberos authentication, the Service Principal Name (SPN) of the Active Roles Administration Service must be added to the service account (domain user account under which the Administration Service runs). For example, suppose that:

  • arsrv.domain.com is the FQDN of the computer running the Administration Service.

  • arsrv is the name of the computer running the Administration Service.

SPNs must be added to the service account:

  • aradminsvc/arsrv.domain.com

  • aradminsvc/arsrv

You can add the SPNs to the service account by using the Setspn command line tool:

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

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

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

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

Enabling claim support

Claims-based authorization requires:

  • A domain controller (or controllers) running a version of Windows Server supported by Active Roles, with claim support enabled. For the list of supported operating system, see System Requirements in the Active Roles Release Notes.

  • (Optional) If you need to use device claims, then a domain-joined client computer (or computers) running a supported version of the Windows operating system.

Domain controller requirements for claims-based authorization

The claims-based authorization mechanism has the following requirements on the domain controller (DC) side:

  • Extensions to Active Directory, such as claim type objects intended to store the claim configuration data. By adding a Windows Server domain controller (DC), you extend the Active Directory schema to provide the object classes and attributes required to support claims-based authorization.

  • Enhancements in the Kerberos Key Distribution Center (KDC) and Security Accounts Manager (SAM) that enable DCs running Windows Server to recognize claim types, retrieve claim information, and transport claims within Kerberos tickets.

    A Windows Server DC that supports claim issuance understands claim types published in Active Directory. Claim types define the claim source attributes. When servicing an authentication request, the domain controller reads the source attribute from the claim type and retrieves the attribute data for the authenticating user. Then, the retrieved attribute data is included in the Kerberos ticket and returned to the requestor.

  • If the DC does not support claim issuance by default, you must enable it via Group Policy. The Group Policy setting that serves this purpose is located in Computer Configuration > Policies > Administrative Templates > System > KDC > KDC support for claims, compound authentication and Kerberos armoring. Enable this policy setting in a Group Policy Object applied to the Domain Controllers Organizational Unit (for example, in the Default Domain Controllers Policy object), and confirm that this policy setting has the Supported option selected.

NOTE: Claims-based authorization does not impose domain or forest functional requirements. If your Active Directory domain has a sufficient number of Windows Server DCs to service authentication requests that include claim information, then you can make use of Windows claims.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione