Chatee ahora con Soporte
Chat con el soporte

Active Roles 8.1.1 - Administration Guide

Introduction 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
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 Configure 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 Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Managing Hybrid AD users
Creating a new Azure AD user with the Web Interface Viewing or updating the Azure AD user properties with the Web Interface Viewing or modifying the manager of a hybrid Azure user Disabling an Azure AD user Enabling an Azure AD user Deprovisioning of an Azure AD user Undo deprovisioning of an Azure AD user Adding an Azure AD user to a group Removing an Azure AD user from a group View the change history and user activity for an Azure AD user Deleting an Azure AD user with the Web Interface Creating a new hybrid Azure user with the Active Roles Web Interface Converting an on-premises user with an Exchange mailbox to a hybrid Azure user Licensing a hybrid Azure user for an Exchange Online mailbox Viewing or modifying the Exchange Online properties of a hybrid Azure user Creating a new Azure AD user with Management Shell Updating the Azure AD user properties with the Management Shell Viewing the Azure AD user properties with the Management Shell Delete an Azure AD user with the Management Shell Assigning Microsoft 365 licenses to new hybrid users Assigning Microsoft 365 licenses to existing hybrid users Modifying or removing Microsoft 365 licenses assigned to hybrid users Updating Microsoft 365 licenses display names
Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Microsoft 365 roles management for hybrid environment users Managing Microsoft 365 contacts Managing Hybrid AD groups Managing Microsoft 365 Groups Managing cloud-only distribution groups Managing cloud-only dynamic distribution 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 cloud-only shared mailboxes
Modern Authentication 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 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

Entitlement rules

When building a user’s entitlement profile, Active Roles uses a specifier’s entitlement rules to tell whether the user is entitled to the resource represented by that specifier. The rules are evaluated against the entitlement target object. If the object matches the rules, then Active Roles regards the user as entitled to the resource, and adds information about the resource to the user’s entitlement profile.

Entitlement rules can be classified by rule condition as follows:

  • Explicit exclusion: The rule condition is a list of directory objects. If the entitlement target object occurs in that list, it is regarded as not matching the rules.

  • Explicit inclusion: The rule condition is a list of directory objects. If the entitlement target object occurs in that list, it is regarded as matching the rules.

  • Filter-based exclusion: The rule condition is one or more filters each of which represents certain requirements on an object’s location and properties. If the entitlement target object satisfies the requirements of at least one filter, then it is regarded as not matching the rules.

  • Filter-based inclusion: The rule condition is one or more filters each of which represents certain requirements on an object’s location and properties. If the entitlement target object satisfies the requirements of at least one filter, then it is regarded as matching the rules.

For more information on how Active Roles applies entitlement rules, see About entitlement profile build process.

Resource display

For each resource that is to be included in the entitlement profile, Active Roles applies entitlement rules to single out the appropriate specifier and then it uses the resource display settings of that specifier to build the entitlement profile’s section that displays information about the resource.

The resource display settings include the following:

  • Resource type icon: Graphics that helps distinguish the type of the resource in the entitlement profile.

  • Resource type name: Text string that identifies the type of the resource in the entitlement profile.

  • Resource naming attribute: Entitlement target object’s attribute whose value is used to identify the resource in the entitlement profile.

  • Other resource-related attributes: List of the entitlement target object’s attributes whose values are to be displayed in the entitlement profile.

The entitlement profile’s section for a given resource is divided into two areas:

  • Heading: Displays the resource type icon, resource type name, and value of the resource naming attribute.

  • Details: Lists the names and values of the resource-related attributes.

The Details area can be customized by adding HTML code to a certain attribute of the user account for which the entitlement profile is being built. The LDAP display name of that attribute should be supplied in the edsaHTMLDetailsAttribute of the entitlement profile specifier. As a result, Active Roles renders that HTML code instead of displaying the attributes list in the Details area.

About entitlement profile build process

When requested to build a user’s entitlement profile, Active Roles performs the following steps.

  1. Prepare a list of the user’s groups, that is, a list of the security groups to which the user belongs whether directly or because of group nesting.

  2. Prepare a list of the user’s managed objects, that is, a list of the directory objects for which the user is assigned as the primary owner (manager) or a secondary owner.

  3. For each entitlement profile specifier of the personal resource entitlement type, evaluate the entitlement rules of that specifier against the user’s account. If the user’s account matches the entitlement rules, then add information about the resource to the entitlement profile, presenting the resource in accordance with the resource display settings found in the specifier.

  4. For each of the user’s groups, apply the entitlement profile specifiers of the shared resource entitlement type as follows:

    1. For each specifier, evaluate the entitlement rules of that specifier against the group.

    2. Once a specifier has been found such that the group matches its entitlement rules, then add information about the resource to the entitlement profile, presenting the resource in accordance with the resource display settings held in the specifier.

    3. If the group matches the entitlement rules of more than one specifier, apply the first specifier found and disregard the others.

  5. For each of the user’s managed objects, apply the entitlement profile specifiers of the managed resource entitlement type as follows:

    1. For each specifier, evaluate the entitlement rules of that specifier against the managed object.

    2. Once a specifier has been found such that the managed object matches its entitlement rules, then add information about the resource to the entitlement profile, presenting the resource in accordance with the resource display settings held in the specifier.

    3. If the managed object matches the entitlement rules of more than one specifier, apply the first specifier found and disregard the others.

Entitlement rules play a central part in the process of building the entitlement profile. It is the entitlement rules that determine whether Active Roles regards a given user as entitled to a given resource, and thus adds information about that resource to the user’s entitlement profile. When evaluating entitlement rules against a particular object, Active Roles performs the following steps.

  1. Apply the explicit exclusion rules. If the object is in the list of excluded objects, then disregard the remaining rules, and mark the object as not matching the rules. Otherwise, proceed to the next step.

  2. Apply the explicit inclusion rules. If the object is in the list of included objects, then disregard the remaining rules, and mark the object as matching the rules. Otherwise, proceed to the next step.

  3. Apply the filter-based exclusion rules. If the object satisfies the rule condition, then disregard the remaining rules, and mark the object as not matching the rules. Otherwise, proceed to the next step.

  4. Apply the filter-based inclusion rules. If the object satisfies the rule condition, then mark the object as matching the rules.

It may occur that the entitlement target object matches the entitlement rules of more than one specifier. In this case, Active Roles needs to choose a single specifier from those matching the entitlement target object. This is accomplished as follows:

  1. Examine the edsaPriority attribute of each specifier, and look for specifiers that have edsaPriority not set. If no such specifier found, then proceed to Step 3. If a single specifier found, then apply that specifier. Otherwise, proceed to Step 2.

  2. Range the specifiers that have edsaPriority not set in ascending alphanumeric order by name, and apply the specifier that goes first. Do not perform Steps 3–4.

  3. Choose the specifiers with the lowest edsaPriority value. If a single specifier has the lowest edsaPriority value, then apply that specifier. Otherwise, proceed to the next step.

  4. Range the specifiers with the lowest edsaPriority value in ascending alphanumeric order by name, and apply the specifier that goes first.

NOTE: Specifiers that have edsaPriority not set take precedence over those for which edsaPriority is set.

Once Active Roles has identified a single specifier for entitlement to a given resource, it uses the resource display settings of the specifier to build a section of the entitlement profile that displays information about the resource. If multiple resources match a particular specifier, then the sections specific to those resources are grouped together in an expandable block, to prevent the entitlement profile display from cluttering.

Entitlement profile configuration

In Active Roles, entitlement profile specifiers provide the ability to store the definition of entitlement to a particular resource in a single object. entitlement profile specifiers determine the contents of the entitlement profile.

When building the entitlement profile of a given user, Active Roles uses the entitlement profile specifiers to determine what resources the user is entitled to, and what information about each resource is to be shown in the entitlement profile.

Active Roles comes with a collection of predefined specifiers, and allows administrators to create additional specifiers or change existing specifiers. You can use the following instructions to create or change entitlement profile specifiers:

For a list of pre-defined specifiers, see Predefined specifiers.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación