Chat now with support
Chat mit Support

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

Step 2: Configuring the membership rules

In this scenario, employees working in Seattle have user accounts with a value of Seattle for the City attribute. Those working in Atlanta have a value of Atlanta.

First, configure the membership rule for the Seattle group. Right-click the group and click Convert to Dynamic Group. In the confirmation message box, click Yes.

On the first page of the New Membership Rule wizard, click Include by Query, and then click Next.

On the second page, click Add to display the Create Membership Rules dialog box. Then, follow these steps to configure the membership rule:

  1. In the Find list, click Users.
  2. Click Browse and select the domain, OU, or Managed Unit that holds user accounts of the employees.
  3. Click the Advanced tab.
  4. Click Field, click City, and then click OK in the Select Object Property dialog box.
  5. In the Condition list, click Is (exactly).
  6. In the Value box, type Seattle.
  7. Click Add, and then click the Add Rule button.

When you are done, click Finish in the New Membership Rule wizard.

Repeat the same procedure for the Atlanta group, but type Atlanta in the Value box when configuring the membership rule.

Active Roles Reporting

Introduction

The Active Roles reporting solution leverages Microsoft SQL Server Reporting Services (SSRS) as a platform for managing, generating, and viewing reports.

Through the use of SSRS, Active Roles delivers enterprise reporting functionality that combines the strengths of Web-based features and traditional reporting. The use of Reporting Services provides a way to centralize report storage and management, enable secure access to reports, control how reports are processed and distributed, and standardize how reports are used.

A comprehensive collection of report definitions, referred to as the Active Roles Report Pack, are published to the report server, a component of Reporting Services. Installing the Report Pack creates published reports that can be accessed through Web addresses (URLs), through SharePoint Web parts, or through Report Manager, a Web-based report access and management tool included with SSRS.

Opening a published report from the report server generates the report in a format suitable for viewing. This action is referred to as rendering a report. Rendering a report also occurs upon subscription, when the report is delivered to an e-mail inbox or a file share in an output format specified by the report user.

The reports that can be generated once the Active Roles Report Pack is deployed are instrumental in change tracking audits, directory data monitoring and analysis, and assessment of Active Roles security and policy configurations. The reports fall into these categories:

  • Active Roles Tracking Log  Check what changes were made to directory data through the use of Active Roles, who made the changes, and when the changes were made.
  • Active Directory Assessment  Examine the state of directory data, such as properties of users, groups and other directory objects, group membership lists, and contents of organizational units.
  • Administrative Roles  View details on who has access to what data when using Active Roles, and what changes administrative users or groups are authorized to make.
  • Managed Units  View details on the Managed Units defined in the Active Roles environment, what policies are applied to Managed Units, and what users or groups have administrative access to what Managed Units.
  • Policy Objects  View details on what administrative policies are defined in the Active Roles environment, where particular policies are applied, and what policies are in effect on particular objects and containers.
  • Policy Compliance  View details on what data in the directory is not compliant with Active Roles policies that are in effect, and what policy rules are violated.

Reports are built on data prepared by the Active Roles Collector. For details about the Active Roles Collector, see Collector to prepare data for reports later in this chapter.

You can generate and view reports by using Report Manager, which is part of SSRS. For instructions on how to generate and view reports, see Working with reports later in this chapter.

Collector to prepare data for reports

The Active Roles Collector allows you to collect data from computers running the Administration Service and store it in an on-premises or Azure SQL database, making the data available for reporting.

NOTE: The Collector is installed as a separate component of Active Roles.

Data for reports is collected from the following sources:

  • Active Directory  The Collector accesses Active Directory through the Administration Service. Reports built on this data provide detailed information about domains, accounts, groups, and other Active Directory objects.
  • Active Roles configuration database  Reports built on this data provide detailed information about who can carry out what actions and to which directory objects using Active Roles, as well as information about the policies defined by Active Roles.
  • Event log on computers running the Administration Service  Reports built on this data provide detailed information about actions performed, the success or failure of each action, and object properties that were modified using Active Roles.

The scope of data that the Collector can retrieve from Active Directory is restricted by the access rights of the user account under which the Collector performs the data collection task. Therefore, reports based on Active Directory data only include information about the objects that the Collector is permitted to access in Active Directory.

For example, suppose the Collector performs a data collection task under the user account that is not permitted to access user account properties in Active Directory. As a result, the Collector will not be able to retrieve data related to user accounts, and reports will not display any information about user accounts, including the number of user accounts.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen