Active Roles supports the following SQL Server topologies.
-
Standalone
-
Multiple SQL Servers
TIP: One Identity recommends implementing a fault tolerant configuration such as:
You can install Active Roles Web Interface either on the machine where Active Roles Administration Service is running, or on a standalone server. However, when Active Roles Web Interface is installed on a standalone server, the following limitations apply:
|
CAUTION: Hazard of data loss!
Active Roles client components are version-specific. Using mismatched or older versions can lead to a loss of functionality or data corruption. |
Make sure that all Active Roles client components are up-to-date. The supported client components include:
To check the version of Active Roles client components
-
Open the Active Roles Console.
-
To check the list of all clients currently connected to the Active Roles service, navigate to Server Configuration > Client Sessions.
-
In the Client Version column, take note of any older clients, and upgrade them immediately.
The Active Roles Web Interface supports the following federated authentication options:
WS-Federation can be used with Microsoft Entra ID or Active Directory Federation Services (ADFS). SAML 2.0 Authentication can utilize any SAML provider, like OneLogin by One Identity.
You can configure Active Roles Web Interface to use SAML 2.0 Authentication with a number of common Identity Providers. The provider can then request both primary and secondary authentication. For more information, see the Active Roles Administration Guide.
Additional third-party providers can be configured using the Redistributable Secure Token Server (RSTS).
For more information of federated authentication, see Configuring federated authentication in the Active Roles Administration Guide.