지금 지원 담당자와 채팅
지원 담당자와 채팅

Active Roles 7.4.1 - 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 License Management Office 365 Roles Management 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_Overview
Config ARS to Manage Hybrid AD Objects Managing Hybrid AD Users Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Azure O365 or Unified Groups
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 delegation for Federated Authentication

Access to Web Interface

If you want to access the Active Roles Web Interface through a firewall, then you need to open the following ports:

  • Port 80 (Default HTTP) TCP Inbound/Outbound
  • Port 443 (Default HTTPS) TCP Inbound/Outbound

The Web Interface normally runs over port 80, or over port 443 if SSL is enabled (off by default).

 

Appendix D: Active Roles and supported Azure environments

This section explains about the different types of Azure environment configurations supported by Active Roles and examples of each configuration.

Active Roles supports the following Azure environment configurations:

Non-Federated

An environment in which, the on-premise domains are not registered in Azure AD and Azure AD Connect or any third party synchronization tools are not configured in the domain for synchronization is called as a Non-federated environment. The changes made in Active Roles are immediately replicated to Azure or Office 365 using Graph API Calls or Command-let calls. Users are typically created in Azure with onmicrosoft.com UPN suffix. It is less likely to have this type of environment in production and can be used only for testing.

Examples of non-federated configuration

  • On-premise Domain: test.local

  • Azure AD Domain: ARSAzure.onmicrosoft.com

  • Azure AD Connect: Not present in the domain

The domain is not registered in Azure. The user is created in Active Roles with an id: user001@test.local and in Azure as user001@ARSAzure.onmicrosoft.com. The user is created in Azure simultaneously when it is created in Active Roles using GRAPH API call.

Synchronized Identity

In a Synchronized Identity, the on-premise domain may or may not be registered in Azure AD. Here Azure AD Connect is configured to synchronize the local AD objects to Azure. Users may typically be created with selected on-premises domains or onmicrosoft.com UPN suffix.

Figure 122: Synchronized identity configuration

Synchronized Identity configuration

Examples of Synchronized Identity configuration

  • On-premise Domain: test.local
  • Azure AD Domain: rd4.qsftdemo.com
  • Azure AD Connect performs the synchronization task.

The On-premise domain may or may not be registered in Azure. User will be created in Active Roles with id: user001@test.local and in Azure as user001@rd4.qsftdemo.com.

Federated

In a Federated environment, the on-premises domain will be registered in Azure AD. Azure AD Connect and ADFS are configured to facilitate synchronization. Users are typically created with the UPN suffix of the selected on-premises domain.

Figure 123: Federated configuration

Federated environment configuration

Examples of Federated configuration

  • On-premise Domain: rd4.qsftdemo.com
  • Azure AD Domain: rd4.qsftdemo.com
  • Azure AD Connect and AD FS are configured.

The domain is registered and verified in Azure. The User is created in Active Roles and Azure AD with the same id: user001@rd4.qsftdemo.com

Azure Object Management supported in various Azure environments

This section provides information about the supported operations and methods for performing the operations for Azure objects in various Azure environments using Active Roles Web interface, such as Federated, Synchronized Identity, and Non-Federated environments.

In Active Roles Web interface, the required Azure environment configuration can be selected during the Azure tenant creation. The specified configuration can be modified later if needed by changing the Azure properties of the tenant.

Active Roles identifies the environment based on the Azure Tenant type and applies the changes to the Web interface.

 

 

Azure Object Management in Non-Federated environment

Non-federated environment is used generally for testing purposes. In non-federated environment, most of the Azure properties can be modified, other than attributes such as UserPrincipalName and ObjectId which identify the object uniquely.

The following table provides information about the operations and methods of operation that can be performed on Azure Objects in a non-federated environment.

 

Table 116: Supported Azure configurations comparison chart
Object Operation Non-Federated : Method
User Create Using GRAPH API
Read Using GRAPH API and Exchange Online Command-lets
Update Using GRAPH API and Exchange Online Command-lets
Delete Using GRAPH API
Security Group Create Using GRAPH API
Read Using GRAPH API
Update Using GRAPH API
Delete Using GRAPH API

Mail Enabled Security

Group

Create Using Exchange Online Command-lets
Read Using GRAPH API
Update Using GRAPH API
Delete Using GRAPH API
Distribution Group Create Using Exchange Online Command-lets
Read Using GRAPH API
Update Using GRAPH API
Delete Using GRAPH API

Native Office 365 Group

(Cloud-only*)

 

Create

 Using GRAPH API

Read

 Using GRAPH API

Update

 Using GRAPH API

Delete

 Using GRAPH API
Contacts Create Using Exchange Online Command-lets
Read Using GRAPH API
Update Using Exchange Online Command-lets
Delete Using GRAPH API

 

NOTE: *Active Roles provides cloud-only support only for Office 365 Groups management.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택