Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.9.0 - Administration Guide

Preface Introduction The concepts of SPS The Welcome Wizard and the first login Basic settings User management and access control Managing SPS
Controlling SPS: reboot, shutdown Managing Safeguard for Privileged Sessions clusters Managing a high availability SPS cluster Upgrading SPS Managing the SPS license Accessing the SPS console Sealed mode Out-of-band management of SPS Managing the certificates used on SPS
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search (classic) interface Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The SPS RPC API The SPS REST API SPS scenarios Troubleshooting SPS Configuring external devices Using SCP with agent-forwarding Security checklist for configuring SPS Jumplists for in-product help Third-party contributions About us

Local client-side authentication

Purpose:

To perform authentication locally on SPS for client-side connections, complete the following steps:

NOTE:

The users can be authenticated to their passwords, public-keys or X.509 certificates uploaded to SPS.

The accounts created to access the SPS web interface cannot be used to authenticate SSH connections.

Prerequisites:

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.

Steps:
  1. Navigate to SSH Control > Authentication Policies, and select the authentication policy to modify.

  2. Select Authenticate the client to PSM using > Local user database, and select the permitted authentication methods (Password, Public key, X.509 certificate).

  3. Select the Local user database from the list that defines the users who can access the server.

  4. Click Commit.

Relayed authentication methods

For the server-side connection (between SPS and the target server), the following authentication methods are available.

NOTE:

Even though these settings refer to the server-side connection, the client must support the selected authentication method and have it enabled. For example, to use publickey authentication on the server side, the client must support publickey authentication as well as provide a 'fake' publickey, even if a different authentication method is used on the client side.

The Connection Policy will ignore the settings for server-side authentication (set under Relayed authentication methods) if a Credential Store is used in the Connection Policy.

Figure 185: SSH Control > Authentication Policies — Configuring relayed authentication methods

  • Password: Authentication based on username and password. The server will request a password from the user, even if a password-based authentication was already successful on the client-side.

  • Keyboard-Interactive: Authentication based on exchanging messages between the user and the server. This method includes authentication schemes like S/Key or TIS authentication. Note that depending on the configuration of the SSH server, password-based authentication can also require using the keyboard-interactive authentication method.

  • Public Key: Authentication based on public-private encryption keypairs.SPS supports the following public-key authentication scenarios:

    One Identity recommends using 2048-bit RSA keys (or stronger).

    • Agent: Allow the client to use agent-forwarding, and use its own keypair on the server-side. If this option is used, SPS requests the client to use its SSH agent to authenticate on the target server.

      NOTE:

      Agent-based authentication can be combined with other authentication methods in the same Authentication Policy.

      If the provided keys are accepted for authentication, fallback to other authentication methods, for example password is not possible.

      NOTE:

      To perform agent-based authentication on the target server, it is not required to enable the Agent-forwarding channel in the Channel Policy used by the connection. The Agent-forwarding channel is needed only to establish connections from the target server to other devices and authenticate using the agent running on the client.

    • Fix: Use the specified private key in the server-side connection. Select Relayed authentication methods > Public key > Server side private and public key > Fix > Private key, and click to upload the private key.

    • Publish to LDAP: SPS generates a keypair, and uses this keypair in the server-side connection. The public key of this keypair is also uploaded to the LDAP database set in the LDAP Server of the connection policy. That way the server can authenticate the client to the generated public key stored under the user's username in the LDAP database. Select Relayed authentication methods > Public key > Server side private and public key > Publish to LDAP.

      NOTE:

      SPS generates a keypair for every user of the connection policy, not for every session.

  • X.509 certificate: Authentication based on X.509 certificates.SPS supports the following certificate-based authentication scenarios:

    One Identity recommends using 2048-bit RSA keys (or stronger).

    • Agent: Allow the client to use agent-forwarding, and use its own certificate on the server-side. If this option is used, SPS requests the client to use its SSH agent to authenticate on the target server.

      NOTE:

      Agent-based authentication can be combined with other authentication methods in the same Authentication Policy.

      If the provided keys are accepted for authentication, fallback to other authentication methods, for example password is not possible.

      NOTE:

      To perform agent-based authentication on the target server, it is not required to enable the Agent-forwarding channel in the Channel Policy used by the connection. The Agent-forwarding channel is needed only to establish connections from the target server to other devices and authenticate using the agent running on the client.

    • Fix: Use the specified private key and certificate in the server-side connection. Select Relayed authentication methods > X.509 certificate > Server side certificate > Fix, and click to upload the private key and the certificate.

    • Generate: SPS generates an X.509 certificate and the corresponding private key for every connection policy, and uses this certificate in the server-side connections. Select Relayed authentication methods > X.509 certificate > Server side certificate > Generate, and select the certificate authority to use for signing the generated certificates with from the Signing CA field. For details on configuring signing CAs, see Signing certificates on-the-fly.

    • Publish to LDAP: SPS generates an X.509 certificate and the corresponding private key for every connection policy, and uses this certificate in the server-side connections. The certificate is also uploaded to the LDAP database set in the LDAP Server of the connection policy. That way the server can authenticate the client to the generated certificate stored under the user's username in the LDAP database. Select Relayed authentication methods > X.509 certificate > Server side certificate > Publish to LDAP, and select the certificate authority to use for signing the generated certificates with from the Signing CA field. For details on configuring signing CAs, see Signing certificates on-the-fly.

      NOTE:

      SPS generates a certificate for every connection policy, not for every session.

Configuring your Kerberos environment

Purpose:

To integrate SPS with your Kerberos environment, so that your clients can authenticate on the target servers using Kerberos tickets, you have to configure your environment appropriately. Complete the following steps.

Steps:
  1. Configure your DNS server.

    1. On your Domain Name Server (DNS), add SRV records that describe which Key Distribution Center (KDC) belongs to the domain. Add both TCP and UDP entries for each domain. For example, if your domain is example.com and the hostname of your KDC server is kdc.example.com, this entry looks like:

      _kerberos_tcp_example.com 0 0 88 kdc.example.com
      _kerberos_udp_example.com 0 0 88 kdc.example.com
    2. If your environment uses multiple realms, repeat the previous step for every realm.

    3. Verify that the servers that your clients will connect to via SPS have proper reverse-dns entries. Otherwise, your clients cannot access the target servers if you use the Inband destination selection feature of SPS.

  2. Create a keytab file for SPS.

    1. On your KDC server, create a principal for the SPS host, using the domain name of your SPS. For example:

      host/scb.example.com@EXAMPLE.COM
    2. If your environment uses multiple realms, repeat the previous step on the KDC of every realm.

    3. Export the key of the principal into a keytab file.

    4. If your environment uses multiple realms, merge the keytab files of the different realms into a single file, for example, using the ktadd or the ktutil utilities.

    5. If your environment uses multiple realms, repeat the previous step on the KDC of every realm.

  3. Configure the SSH application of your client hosts to enable Kerberos (GSSAPI) ticket forwarding. (In most applications this is disabled by default.)

Expected result:

You have configured your environment to use Kerberos authentication with SPS, and created a keytab file for your SPS host. For details on uploading the keytab file and configuring SPS see Kerberos authentication settings.

Kerberos authentication settings

Purpose:

To perform authentication with Kerberos, complete the following steps:

NOTE:

If Kerberos authentication has been configured for the connection, it is not possible to fall back to other authentication methods.

Prerequisites:

Before configuring Kerberos authentication on SPS, make sure you have configured your Kerberos environment correctly and have retrieved the keytab file. For details, see Configuring your Kerberos environment.

Steps:
  1. Navigate to SSH Control > Authentication Policies.

  2. Create a new Authentication Policy and enable GSSAPI-based single sign-on. This will disable all other authentication methods. Click Commit.

  3. Navigate to SSH Control > Global Options > GSSAPI.

  4. Browse for the Kerberos keytab file, and click Upload. The uploaded principals are displayed in Currently uploaded principals.

    If a Connection Policy uses an SSH Authentication Policy with GSSAPI-based single sign-on together with a Usermapping Policy, then SPS stores the user principal as the gateway user, and the target username as the server username in the session database. If you want to allow your users to use a username on the target server that is different from their principal, configure a Usermapping Policy for your SSH connections. For details, see "Configuring usermapping policies" in the Administration Guide.

  5. Optional step: If more than one realm is deployed on your network, you have to specify the mapping from the server's DNS domain name to the name of its realm. To map hostnames onto Kerberos realms, click .

  6. Navigate to SSH Control > Connections and configure the SSH connection as follows. For details on configuring connections in general, see Configuring connections.

    1. Select Use fixed address or Inband destination selection as Target.

    2. Select the Kerberos Authentication policy.

Related Documents