Configuring federated authentication
You can access an application or websites 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 Configuring federated authentication.
Starling Join configuration task
Active Roles version 8.1.5 supports integration with One Identity Starling services. The Starling Join feature in Active Roles now enables you to connect to One Identity Starling, the Software as a Service (SaaS) solution of One Identity. The Starling Join feature enables access to the Starling services through Active Roles, allowing to benefit from the Starling services such as Two-factor Authentication and Identity Analytics and Risk Intelligence.
You can use the Active Roles Configuration Center to join One Identity Starling to Active Roles on the Starling wizard.
To start the wizard, click Configure in the Starling area on the Dashboard page in the Configuration Center main window. The Starling wizard enables you to perform the Starling join operation.
For more information on configuring Starling join for Active Roles, see Configuring Active Roles to join One Identity Starling.
Active Roles Console access management
On installing Active Roles on a computer, the Active Roles Console user access setting is not enabled by default, and any user is enabled to log in to the Active Roles Console. You can use Configuration Center, to set the Active Roles Console user access.
To manage the Active Roles Console access
-
On the Dashboard page in the Configuration Settings main window, in the MMC Interface Access area, click Manage Settings.
-
On the MMC Interface Access page that opens, in the Settings area, click Component, then click Modify or double-click Component.
-
On the MMC Interface Access wizard that is displayed, select one of the following options:
-
Allow Console (MMC Interface) access for all users: Enables user to log in to Active Roles Console.
-
Restrict Console (MMC Interface) access for all users: Selecting this option restricts all non-Active Roles Administrators from using the Console. All delegated users are affected, however, it does not apply to Active Roles Administrators.
-
Click OK.
The Active Roles Console Access settings get configured successfully. A message is displayed prompting you to restart the Administrative Service to disconnect the current Active Roles Console user sessions and for the updated settings to be reflected on the Active Roles Console.
NOTE: Consider the following when managing Active Roles Console:
-
The user must be delegated with the User Interfaces access rights on the User Interfaces container under Server Configuration to obtain access to the Active Roles Console. User Interfaces Access Templates that provide the access rights are available as part of the Active Roles built-in Access Templates in the User Interfaces container.
-
For information on delegating Console access to specified users, see Delegating control to users for accessing Active Roles Console.
Logging management tasks
Active Roles writes most events to its own Event log in Windows Event Viewer, under Applications and Services, called Active Roles Admin Service. You can use this Event log to help determine root causes for issues and typically provide more detailed error information if any issues are encountered within the Console or the Web Interface.
In addition to the Event log, there is a debug option for the Active Roles Administration Service that is disabled by default. Enabling logging can be accessed either in the Active Roles Console or in the Configuration Center.
Use the Configuration Center to enable, disable or view diagnostic logs for the Active Roles components that are installed on the computer running Configuration Center. On the Logging page, the Configuration Center lists the following information:
-
Component: Name of the component, such as Administration Service, Web Interface or Console.
-
Logging: Indicates whether logging is enabled or disabled for the given component, and the logging level, such as Basic or Verbose.
-
Log location: Depending upon the component, identifies either the folder containing the log files or the log file for that component.
The toolbar on the Logging page allows you to perform the following tasks:
-
To enable or disable logging for a given component, select the component in the list, and then click Modify on the toolbar.
-
To open the folder that contains the log file or files for a given component, select the component in the list, and then click Browse with Explorer on the toolbar.
-
To examine the Administration Service log file in Log Viewer, select Administration Service in the list of components, then click Open in Log Viewer on the toolbar. For more information, see Active Roles Log Viewer.