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
-
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.
-
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.
-
To configure the federated authentication settings, click Federated.
-
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.
-
From Options, select the required additional options.
-
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.
-
To test the connection, click Test metadata.
If the connection is successful, a message is displayed.
-
To view the metadata URL, click Yes. To proceed further with the settings, click No.
-
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.
-
In the Realm field, enter the realm URL of the requesting realm.
-
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.
-
In Claim editor, to add claims, click Add.
The Add claim window is displayed.
-
From the Claim type drop-down, select the type of claim.
IMPORTANT: Active Roles supports UPN, EMAIL, SID, and GUID claims.
-
Select the Claim value.
-
In the Display name field, enter a name for the claim.
-
In the Claim description field, enter a description.
-
Click Save.
The claim is added successfully.
NOTE: You can modify or remove the claims that are created.
-
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.
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/
This section provides a list of communication ports that need to be open in the firewall for Active Roles to function properly.
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 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.
Access to Exchange servers
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
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
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