Get Live Help
An authentication policy is a list of authentication methods that can be used in a connection. Connection definitions refer to an authentication policy to determine how the client can authenticate to the target server. Separate authentication methods can be used on the client and the server-side of the connection.
Figure 189: Authentication policies
Creating a new authentication policy
Client-side authentication settings
Local client-side authentication
Relayed authentication methods
Configuring your Kerberos environment
The following describes how to create a new authentication policy.
To create a new authentication policy
Navigate to SSH Control > Authentication Policies, and click .
Figure 190: SSH Control > Authentication Policies — Configuring authentication policies
Enter a name for the policy into the Name field.
Select the authentication method used on the client-side in the Authenticate the client to SPS using field. For details on the client-side authentication settings, see Client-side authentication settings.
Select the authentication method used on the server-side in the Relayed authentication methods field. For details on the relayed authentication settings, see Relayed authentication methods.
If you selected Public key > Agent as the relayed authentication method:
If this option is used, SPS requests the client to use its SSH agent to authenticate on the target server. Therefore, you must configure your clients to enable agent forwarding, otherwise authentication will fail. For details on enabling agent forwarding in your SSH application, see the documentation of the application.
For the client-side connection, One Identity Safeguard for Privileged Sessions (SPS) can authenticate the client inband (within the SSH protocol) using the following authentication methods:
Figure 191: SSH Control > Authentication Policies — Configuring client-side authentication methods
LDAP: SPS will authenticate the client to the LDAP database set in the LDAP Server of the connection policy. To use LDAP authentication on the client side, select Authenticate the client to SPS using > LDAP, and select the permitted authentication methods (Password, Public key). More than one method can be permitted.
Local user database: Authenticate the client locally on the SPS gateway. For details, see Local client-side authentication.
RADIUS: SPS will authenticate the client to the specified RADIUS server. Select Authenticate the client to SPS using > RADIUS, enter the IP address or hostname of the RADIUS server into the Address field, the port number of the RADIUS server into the Port field, and the shared secret of the RADIUS server into the Shared secret field. Only password-authentication is supported (including one-time passwords), challenge-response based authentication is not.
To use the Password Authentication Protocol, select PAP. To use the Challenge-Handshake Authentication Protocol, select CHAP.
Use an IPv4 address.
To add more RADIUS servers, click and fill in the respective fields.
None: Do not perform client-side authentication, the client will authenticate only on the target server.
Hazard of security breach. If the None authentication option is selected on the client side and SPS is configured to use public-key or certificate based authentication on the server, the user will not be authenticated at all unless gateway authentication is required for the connection.
To use certificates to authenticate the client, you can use the LDAP and the Local user database backends.
Figure 192: Client-side inband gateway authentication with different certificates
|Trusted CA list is set in the Authentication Policy|
|The certificate shown by the client is self-signed AND the user is in the Local User Database and has a self-signed certificate set in the database||successful||successful|
|The certificate shown by the client is CA-signed||successful||unsuccessful|
The following describes how to perform authentication locally on One Identity Safeguard for Privileged Sessions (SPS) for client-side connections.
The users can be authenticated to their passwords or public-keys uploaded to SPS.
The accounts created to access the SPS web interface cannot be used to authenticate SSH connections.
To perform authentication locally on SPS for client-side connections, an existing Local User Database is needed. To create a Local User Database, complete the following procedure: Creating a Local User Database.
To perform authentication locally on SPS for client-side connections
Navigate to SSH Control > Authentication Policies, and select the authentication policy to modify.
Select Authenticate the client to SPS using > Local user database, and select the permitted authentication methods (Password, Public key).
Select the Local user database from the list that defines the users who can access the server.