Chat now with support
Chat with Support

Active Roles 8.0 LTS - 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 Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users 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 Microsoft 365 Groups Managing Azure Security Groups Managing cloud-only distribution 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
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: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta Active Roles Language Pack

Working with federated authentication

Federated authentication allows users to access applications or websites by authenticating them against a certain set of rules, known as claims. The authentication ticket or the token validates the user across multiple applications, websites, or IT systems.

Claim-based authentication is a method to acquire the user's identity-related information on both on-premises and cloud-based products. A single token is created based on the predefined claims to identify the users trying to access the application or website. After the identification of the user is complete, a security token service is used to identify the type of user.

Active Roles supports federated authentication using the WS-Federation protocol, through which you can sign in to an application once using the single sign-on option and you are authenticated to access websites.

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 settings 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: UPN, SID, and email claims are supported.

  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 ARSWeb is modified and is 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/

Role-based Administration

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating