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

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

Configuring federated authentication settings

To configure the federated authentication settings, configure the Identity provider configuration, and set claims in the Claim editor.

NOTE: To access the Active Roles Web Interface for federated authentication purposes, you can use any of the following supported web browsers: Google Chrome, Mozilla Firefox, or Microsoft Edge on Windows 10.

To set identity provider configuration

  1. In the Active Roles Configuration Center main window, click Web Interface.

    The Web Interface page displays all the Active Roles Web Interface sites that are deployed on the web server running the Active Roles Web Interface.

  2. To configure the federated authentication settings, click Authentication.

    The Site authentication settings page is displayed.

    NOTE: By default, the Default Windows authentication setting is configured.

  3. To configure the federated authentication settings, click Federated.

  4. In Identity provider configuration, from the Identity provider drop-down, select the security identity provider. The available options are Azure, ADFS, and Custom.

    NOTE: For the Custom identity provider option, Active Roles supports the WS-Federation standard. However, One Identity Support cannot assist with custom WS-Federation-related configurations of third-party identity providers. For assistance in configuring Active Roles with a custom WS-Federation-related configuration of a third-party identity provider, contact One Identity Professional Services.

  5. From Options, select the required additional options.

  6. In Federated metadata URL, enter a valid URL.

    NOTE: A federation metadata document is an XML document that conforms to the WS-Federation 1.2 schema. It exposes all data required for an STS implementer.

  7. To test the connection, click Test metadata.

    If the connection is successful, a message is displayed.

  8. To view the metadata URL, click Yes. To proceed further with the settings, click No.

  9. From Options, if you select the Token encryption, you must enter the Certificate thumbprint manually. If the Token encryption option is not selected, this field is not available.

    NOTE: You must enter the Certificate thumbprint manually. Copying the key and pasting in the field is not supported.

  10. In the Realm field, enter the realm URL of the requesting realm.

  11. In the Reply URL field, enter the URL to send a response. A URL that identifies the address at which the relying party (RP) application receives replies from the Security Token Service (STS).

To set claims in the Claim editor

IMPORTANT: By default, the priority of the claim is set based on the order the claims are created. The claim created first has the first priority, the claim created next has the secondary priority, and so on. However, you can move the claims based on the required priority.

  1. In Claim editor, to add claims, click Add.

    The Add claim window is displayed.

  2. From the Claim type drop-down, select the type of claim.

    IMPORTANT: Active Roles supports UPN, EMAIL, SID, and GUID claims.

  3. Select the Claim value.

  4. In the Display name field, enter a name for the claim.

  5. In the Claim description field, enter a description.

  6. Click Save.

    The claim is added successfully.

    NOTE: You can modify or remove the claims that are created.

  7. Click Modify.

    If the operation is completed successfully, a message is displayed.

    After you click Modify, the Web Interface is modified and ready for federated authentication.

Examples of configuring identity providers

See the following examples of configuring the identity providers when using federated authentication.

NOTE: For the Custom identity provider option, Active Roles supports the WS-Federation standard. However, One Identity Support cannot assist with custom WS-Federation-related configurations of third-party identity providers. For assistance in configuring Active Roles with a custom WS-Federation-related configuration of a third-party identity provider, contact One Identity Professional Services.

Azure
  • Metadata url: https://login.microsoftonline.com/<AzureTenantID>/FederationMetadata/2007-06/FederationMetadata.xml

  • realm: spn:<Azure Application ID>

  • replyurl: https://<Web Server Name>/arwebadmin/

Active Directory Federation Services (AD FS)
  • Metadata url: https://<ADFS Server name>/FederationMetadata/2007-06/FederationMetadata.xml

  • realm: https://<Web Server Name>/arwebadmin/

  • replyurl: https://<Web Server Name>/arwebadmin/

Communication ports

This section provides a list of communication ports that need to be open in the firewall for Active Roles to function properly.

Access to the managed environment

If the environment managed by Active Roles is located behind a firewall, then the following ports must be open between the Active Roles Administration Service and managed environment.

For instance, if there is a firewall between Active Roles and DNS, then port 15172 must be open (Inbound/Outbound) on the Active Roles host (or the firewall between Active Roles and Exchange) and port 53 must be open on the DNS server (or the firewall between Active Roles and DNS).

Access to DNS servers
  • Port 53 TCP/UDP Inbound/Outbound

Access to domain controllers
  • Port 88 (Kerberos) TCP/UDP Inbound/Outbound

  • Port 135 (RPC endpoint mapper) TCP Inbound/Outbound

  • Port 139 (SMB/CIFS) TCP Inbound/Outbound

  • Port 445 (SMB/CIFS) TCP Inbound/Outbound

  • Port 389 (LDAP) TCP/UDP Outbound

  • Port 3268 (Global Catalog LDAP) TCP Outbound

  • Port 636 (LDAP SSL) TCP Outbound

    This port is required if Active Roles is configured to access the domain by using SSL.

  • Port 3269 (Global Catalog LDAP SSL) TCP Outbound

    This port is required if Active Roles is configured to access the domain by using SSL.

  • The TCP port allocated by RPC endpoint mapper for communication with the domain controller.

    You can configure Active Directory domain controllers to use specific port numbers for RPC communication. For instructions, see How to restrict Active Directory RPC traffic to a specific port.

  • The following ports must be open for the notifications specific to SaaS-based operations to work. The Web Interface machine should be able to resolve Service machine name for notifications to work.

    • Port 7465 (HTTP) TCP Inbound/Outbound

    • Port 7466 (HTTPS) TCP Inbound/Outbound

Access to Exchange servers
  • Port 135 (RPC endpoint mapper) TCP Inbound/Outbound

  • The TCP port allocated by RPC endpoint mapper for communication with the Exchange server.

You can configure Exchange servers to use specific port numbers for RPC communication. For more information, contact Microsoft Support.

The following ports must be open for operations related to the WinRM service to work:

  • Port 5985 (HTTP) TCP Inbound/Outbound

  • Port 5986 (HTTPS) TCP Inbound/Outbound

  • Port 80 TCP Inbound/Outbound

Computer resource management
  • Port 139 (SMB/CIFS on the managed computers) TCP Inbound/Outbound

  • Port 445 (SMB/CIFS on the managed computers) TCP Inbound/Outbound

Computer restart
  • Port 139 (SMB/CIFS on the managed computers) TCP Inbound/Outbound

  • Port 137 (WINS) UDP Outbound

  • Port 138 (NetBIOS datagrams) UDP Outbound

Home folder provisioning and deprovisioning
  • Port 139 (SMB/CIFS on the servers that host home folders) TCP Inbound/Outbound

  • Port 445 (SMB/CIFS on the servers that host home folders) TCP Inbound/Outbound

Access to SMTP server for email integration
  • Port 25 (Default SMTP port) TCP Outbound

  • Active Roles uses SMTP port 25 by default. The default port number can be changed in the properties of the Mail Configuration object in the Active Roles Console. If Mail Configuration specifies a different port, open that port rather than port 25.

Access to AD LDS instances
  • The TCP port specified when registering the AD LDS instance with Active Roles

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택