Chat now with support
Chat with Support

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

Export a Web Interface site’s configuration object to a file

From the Web Interface page in the Configuration Center main window, you can export site configuration objects: Click an entry in the list of sites and then click Export Configuration on the toolbar. A wizard starts, prompting you to specify the export file. The wizard then retrieves the site’s configuration object from the Administration Service, and saves the data from that object to the export file.

The export file could be considered a backup of the site’s configuration. You can set up a Web Interface site with the configuration restored from an export file, by importing that file on the Configuration step in the wizard for creating or modifying Web Interface sites.

Configure Web interface for secure communication

By default, Active Roles users connect to the Web interface using a HTTP protocol, which does not encrypt the data during communication. However, it is recommended to use a HTTPS protocol to transfer data securely over the web. You can use the Force SSL Redirection option in the Configuration Center to enable secure communication over HTTPS for the Web interface on local or remote servers.

To configure the Web interface for secure communication for the first time

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

    The Web Interface page lists all the Web interface sites that are deployed on the Web server running the Web interface.

  2. To modify the secure communication settings for the sites, click Force SSL Redirection.

    The Manage Force SSL Redirection Settings for sites window is displayed.

  3. In the Available Websites field, select the required web site from the drop-down list.

    The configuration status of the website is displayed.

  1. To enable the force SSL redirection, switch between the Enable Force SSL Redirection states. Turn it on.

    NOTE:

    • If the website is not configured earlier for secure communication, the Enable Force SSL Redirection option is not selected by default and the HTTPS configuration status is shown as Not configured.
    • If the website is configured earlier for secure communication, then the Enable Force SSL Redirection option is selected by default and the HTTPS configuration status shows as Configured.
    • If the website is configured earlier for secure communication, and the SSL bindings was deleted in the IIS site, the Enable Force SSL Redirection option is selected by default. The status Binding Deleted is displayed. In this case, the secure communication must be configured again for the web site.

    The Available HTTPS Bindings field is enabled and displays the list of HTTPS bindings configured for the selected web site in the format: <IP adress, Port, Host name>.

    NOTE:

    • If the selected web site does not have any binding configured, then the Available HTTPS Bindings field remains disabled and a message is displayed indicating that HTTPS bindings are not available and the need to configure the Force SSL Redirection to a valid binding. In this case, HTTPS bindings must be configured for the selected web site from the IIS site before initiating the configuration of secure communication for the web site in Active Roles.
    • If the binding for a configured web site is deleted externally on the IIS site, the Available HTTPS Bindings field is enabled without any binding displayed, and a message is displayed indicating that HTTPS binding is deleted and the Force SSL redirection setting must be reconfigured.
  1. In the Available HTTPS Bindings field, click the drop-down list and select the required binding for the web site.
  2. Click Modify.

    After successful completion of configuration changes, in the Web Interface window, the Force SSL Redirection configuration state for the selected web site is displayed as green and enabled.

  1. Click Finish.

    NOTE: The browser cache must be cleared after any changes are made to SSL settings.

    For the configured web site, any HTTP communication is now redirected to HTTPS automatically.

Disabling secure communication for Web interface sites

Disabling secure communication for Web interface sites

By default, Active Roles users connect to the Web interface using a HTTP protocol, which does not encrypt the data during communication. However, it is recommended to use a HTTPS protocol to transfer data securely over the web. You can use the Force SSL Redirection option in the Configuration Center to enable secure communication over HTTPS for Web interface on local or remote servers.

In case you do not want a secure communication enabled for transferring data over the web, you can disable the HTTPS option using the Force SSL Redirection option in the Configuration Center.

To disable the secure communication for Web interface sites

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

    The Web Interface page displays all the Web interface sites that are deployed on the Web server running the Web interface.

  2. To modify the secure communication settings for the sites, click Force SSL Redirection.

    The Manage Force SSL Redirection Settings for sites window is displayed. The Enable Force SSL Redirection option is enabled after HTTPS configuration.

  3. In the IIS Web site field, select the required web site from the drop-down list.

  4. To disable the force SSL redirection, switch between the Enable Force SSL Redirection states. Turn it off.

  5. Click Modify , and then Finish.

    NOTE: The browser cache must be cleared after any changes are made to the SSL settings.

    After successful completion of the configuration changes, in the Web Interface window, the Force SSL Redirection configuration state for the selected web site is displayed as not configured.

    After disabling the Force SSL Redirection, all communication is now redirected to HTTP.

For more information on secure communication and Federated Authentication, see Working with Federated Authentication.

 

Configuring Federated authentication

You can access an application or web sites by authenticating them against a certain set of rules known as claims, by using the Federated authentication feature. The Federated authentication feature uses the Security Assertion Markup Language (SAML), through which you can sign in to an application once using the single sign-on option and you are authenticated to access websites. For more information, see Working with Federated Authentication.

Related Documents