Chat now with support
Chat with Support

Active Roles 7.5.2 - 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

Appendix H: Active Roles integration with Okta

Active Roles can be integrated with Okta to complement and extend identity and access management. For more information about Okta, see https://www.okta.com/.

Okta is a cloud-based identity service offering identity, authentication, and access control functions as a service. To support functions such as Single Sign-on (SSO) and Multi-Factor Authentication (MFA), Active Roles integrates with the Okta identity management service through Federated Authentication. This enables you to leverage an additional out-of-band factor (typically through the user’s registered smartphone) when authenticating the user. The additional factor is processed in-line with the connection, so users do not have to switch to an external application to process the additional factor. This results in a seamless and efficient user experience that is readily accepted by the users. Okta supports a broad range of authentication methods, including software, hardware, and mobile-based solutions.

By enabling this integration with Okta, Active Roles can use your users' Okta accounts to authenticate them when accessing the Active Roles Web Interface. To enable this functionality with Active Roles, you need to configure it using the Federated Authentication login method in the Active Roles Configuration Center. The MFA functionality is an additional configuration that you need to perform in the Okta Admin Console.

Configuring the Active Roles application in Okta

From version 7.5.2, Active Roles can be integrated with Okta, a cloud-based identity service offering identity, authentication, and access control functions as a service to complement and extend identity and access management.

To configure the Active Roles application in Okta, follow these steps.

To configure the Active Roles application in Okta

  1. Log into the Okta Admin Console.

  2. Navigate to Applications > Applications.

  3. Click Browse App Catalog.

  4. Search for and select Template WS-Fed.

  5. Click Add.

  6. Enter and set the following:

    1. Application label: Enter a label for the Okta application.

    2. Web Application URL: Enter the URL for the Active Roles Web Interface, for example, https://localhost/arwebadmin.

    3. ReplyTo URL: Enter the same URL that you entered as the Web Application URL value.

    4. Name ID Format: Enter Persistent.

    5. Audience Restriction: Temporarily enter the same value that you entered as the Web Application URL value. This will be updated.

    6. Custom Attribute Statements: Enter http://schemas.xmlsoap.org/ws/2005/05/identity/claims/email|${user.email}|.

  7. Click Done.

  8. Click General.

  9. Copy the value from Realm.

  10. Click Edit.

  11. Paste the Realm value as the Audience Restriction value.

  12. Click Save.

  13. Click Sign On.

  14. To open a new tab with information needed to configure WS-Federation in Configuring Okta in the Active Roles Configuration Center, click View Setup Instructions.

NOTE: In Okta, the Active Roles application must be assigned to users so that they can be used for logging in.

Configuring Okta in the Active Roles Configuration Center

From version 7.5.2, Active Roles can be integrated with Okta, a cloud-based identity service offering identity, authentication, and access control functions as a service to complement and extend identity and access management.

To configure Okta in the Active Roles Configuration Center, follow these steps.

Prerequisites

Before you can configure Okta in the Active Roles Configuration Center, you must configure the Active Roles application in Okta. For more information, see Configuring the Active Roles application in Okta.

To configure Okta in the Active Roles Configuration Center

  1. In the Active Roles Configuration Center, navigate to Web Interface > Authentication.

  2. In the Site authentication settings window, select the Federated tab.

  3. In the Identity provider configuration tab that you opened in Step 14 of Configuring the Active Roles application in Okta, configure the settings of the identity provider.

    1. From Identity provider, select Custom.

    2. In Okta Setup Instructions, copy the Public Link URL.

    3. In the Active Roles Configuration Center, paste it into the Federated metadata URL.

    4. To validate the metadata, click Test metadata.

    5. To close the prompt about opening the XML file in a web browser, click No.

  4. In the Okta Setup Instructions tab that you opened in Step 14 of Configuring the Active Roles application in Okta, copy the Realm (APP ID URL) value.

  5. In the Active Roles Configuration Center, paste the Realm (APP ID URL) value as the Realm value.

  6. In Reply URL, enter the same value that you entered as the Web Application URL value in Step 6 of Configuring the Active Roles application in Okta.

  7. In Claim editor, click Add to open the Add claim window, and enter or select the following.

    1. Claim Type: Based on the values of the local AD objects, select UPN or EMAIL.

      NOTE: The UPN or the email address of the local AD objects must match the email value of the Okta objects.

    2. Claim value: Select http://schemas.xmlsoap.org/ws/2005/05/identity/claims/email.

    3. Display name: Enter the display name in user.email format.

    4. Description: Enter any description (this is typically the value the user logged in with).

    5. Click Save.

  8. Click Domain user login credentials.

  9. To access the local domain, enter the Username in domain/username format, and the Password.

  10. Click Modify.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating