Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 6.1.0 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (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 interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS) Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help LDAP user and group resolution in SPS Appendix: Deprecated features

Telnet-specific settings

The following sections describe configuration settings available only for the Telnet protocol. Use the following policies to control who, when, and how can access the Telnet connection. For a list of supported client applications, see Supported protocols and client applications.

  • Channel Policy: The Telnet protocol has only one channel type with no special configuration options. The available channel policy options are the following: Type, From, Target, Time policy, 4 eyes, Record audit trail, Gateway groups, Remote groups, and Content policy. For details on configuring these options, see Creating and editing channel policies.

  • TLS support: To enable TLS-encryption for your Telnet connections, see Enabling TLS-encryption for Telnet connections.

  • Authentication Policy: Authentication policies describe the authentication methods allowed in a connection. Different methods can be used for the client and server-side connections. For details, see Creating a new Telnet authentication policy.

  • Telnet settings: Telnet settings determine the parameters of the connection on the protocol level, including timeout value, and so on. For details, see Creating and editing protocol-level Telnet settings.

  • User lists in Channel Policies: User lists affect Telnet connections only when they are used together with Gateway Authentication. For details, see Configuring gateway authentication.

  • Content Policy: Content policies allow you to inspect the content of the connections for various text patterns, and perform an action if the pattern is found. For example, One Identity Safeguard for Privileged Sessions (SPS) can send an e-mail alert if a specific command is used in a Telnet terminal session. For details, see Creating a new content policy.

  • Authentication and Authorization plugin:

    One Identity Safeguard for Privileged Sessions (SPS) provides a plugin framework to integrate SPS to external systems to authenticate or authorize the user before authenticating on the target server. Such plugins can also be used to request additional information from the users, for example, to perform multi-factor authentication.

    For details, see Integrating external authentication and authorization systems.

Enabling TLS-encryption for Telnet connections

The following steps describe how to enable TLS-encryption in a Telnet connection policy. Note that when using encryption, One Identity Safeguard for Privileged Sessions (SPS) automatically changes the port number of the connection policy to 992.

Prerequisites

Depending on your requirements, one or more of the following might be needed:

  • An X.509 certificate and its private key. SPS can display the same certificate to the peers on both the client and the server side. You can also use different certificates for the client and server sides. Use your own PKI system to generate these certificates, as they cannot be created on SPS. Note that the Common Name of the certificate must contain the domain name or the IP address of SPS, otherwise the clients might reject the certificate.

  • To generate certificates on-the-fly for a connection, a signing certificate authority is required. For details on creating a signing CA, see Signing certificates on-the-fly.

  • To require the peers of SPS to have an X.509 certificate signed by a specific Certificate Authority, a list of the trusted certificate authorities is needed. For details on creating a trusted CA list, see Verifying certificates with Certificate Authorities.

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

To enable TLS-encryption in a Telnet connection policy

  1. Navigate to Telnet Control > Connections and select the connection policy in which you want to enable TLS.

    Figure 198: Telnet Control > Connections — Enabling TLS-encryption for Telnet connections

  2. Set the encryption settings used between the client and SPS in the Client-side transport security settings section.

    • To require encryption, select TLS. When the connection is encrypted, SPS has to show a certificate to the peer.

    • To enable encrypted connections that use the STARTTLS method, select STARTTLS. Note that the peer must use the STARTTLS method. Unencrypted connections will be terminated after a brief period.

  3. Select the certificate to show to the peers.

    • To use the same certificate for every peer, complete the following steps.

      1. Generate and sign a certificate for SPS in your PKI system, and export the certificate and its private key.

      2. Select Use the same certificate for each connection.

      3. Select Private key for host certificate, click and upload the private key.

      4. Select X.509 host certificate, click and upload the certificate.

    • To use a separate certificate for every connection, complete the following steps.

      1. Create a certificate authority that will be used to sign the certificates that SPS shows to the peer. For details, see Signing certificates on-the-fly.

      2. Select Generate certificate on-the-fly.

      3. In the Signing CA field, select the certificate authority to use.

  1. Select how SPS should authenticate the peers.

    • To permit connections from peers without requesting a certificate, select No certificate is required.

    • To permit connections only from peers with a valid certificate that was signed by a specific CA, complete the following steps.

      1. Create a list of trusted Certificate Authorities that will be used to validate the certificates of the peers. For details on creating a trusted CA list, see Verifying certificates with Certificate Authorities.

      2. Select Only accept certificates authenticated by the trusted CA list.

      3. Select the certificate authority list to use in the Trusted CA field.

  1. Set the encryption settings used between SPS and the server in the Server-side transport security settings section.

    • To require encryption, select TLS. When the connection is encrypted, SPS has to show a certificate to the peer.

    • To enable encrypted connections that use the STARTTLS method, select STARTTLS. Note that the peer must use the STARTTLS method. Unencrypted connections will be terminated after a brief period.

  2. Select the certificate to show to the server.

    • If the server does not require a certificate from SPS, select None.

    • To use the same certificate for every peer, complete the following steps.

      1. Generate and sign a certificate for SPS in your PKI system, and export the certificate and its private key.

      2. Select Use the same certificate for each connection.

      3. Select Private key for host certificate, click and upload the private key.

      4. Select X.509 host certificate, click and upload the certificate.

    • To use a separate certificate for every connection, complete the following steps.

      1. Create a certificate authority that will be used to sign the certificates that SPS shows to the peer. For details, see Signing certificates on-the-fly.

      2. Select Generate certificate on-the-fly.

      3. Select the certificate authority to use in the Signing CA field.

    Limitations

    NOTE:

    When using the Use the same certificate for each connection option and the connection policy that allows access to multiple servers using HTTPS, the client applications will display a warning because the certificate used in the connection will be invalid (namely, the Common Name of the certificate will not match the hostname or IP address of the server).

    NOTE:

    Import the certificate of the signing Certificate Authority to your clients. Otherwise, the client applications will display a warning due to the unknown Certificate Authority.

  1. Select how SPS should authenticate the peers.

    • To permit connections from peers without requesting a certificate, select No certificate is required.

    • To permit connections only from peers with a valid certificate that was signed by a specific CA, complete the following steps.

      1. Create a list of trusted Certificate Authorities that will be used to validate the certificates of the peers. For details on creating a trusted CA list, see Verifying certificates with Certificate Authorities.

      2. Select Only accept certificates authenticated by the trusted CA list.

      3. Select the certificate authority list to use in the Trusted CA field.

  1. Click Commit.

    Expected result

    The encryption settings are applied to the connection policy.

Creating a new Telnet authentication policy

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.

To create a new authentication policy

  1. Navigate to Telnet Control > Authentication Policies, and click .

    Figure 199: Telnet Control > Authentication Policies — Configuring Telnet authentication policies

  2. Enter a name for the policy into the Name field.

  3. Select the authentication method used on the client-side in the One Identity Safeguard for Privileged Sessions (SPS)Authenticate the client to SPS using field. For the client-side connection, SPS can authenticate the client inband (within the Telnet protocol) using the following 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.

      NOTE:

      SPS will authenticate the client-side connection to the LDAP server configured in the connection policy. This is not necessarily the same as the LDAP server used to authenticate the users accessing the SPS web interface.

    • Local user database: Authenticate the client locally on the SPS gateway using a Local user database. Select the database to use in the Local user database field. For details on creating a Local User Database, see Creating a Local User Database.

    • 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.

      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.

      Caution:

      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.

  4. Click Commit.

    NOTE:
    • The client-side authentication settings apply for authenticating the user inband (that is, within the SSH protocol) to the SPS gateway, and is independent from the gateway authentication performed on the SPS web interface. The web-based gateway authentication is an out-of-band gateway authentication method that can be required by the connection policy. For details on out-of-band gateway authentication, see Configuring out-of-band gateway authentication.

      Gateway authentication on the SPS web interface can be used together with authentication policies. In an extreme setting, this would mean that the user has to perform three authentications: a client-side gateway authentication within the SSH protocol to SPS, an out-of-band gateway authentication on the SPS web interface, and a final authentication on the target server.

    • 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.

Extracting username from Telnet connections

For specific devices, it is now possible to extract the username from Telnet connections with the help of patterns (including TN3270 and TN5250 systems).

To select patterns or request a custom pattern

  1. Navigate to Telnet Control > Authentication Policies and enable Extract username from the traffic.

  2. Click Select target devices to display the list of available target devices. Select the respective device(s) in the Available devices column and click Add.

    NOTE: You can only add one TN3270 specific device to the authentication policy.

    To remove a device from the Target devices column, select it and click Remove.

  3. Click OK. The target devices are listed after Selected devices.

  4. If you cannot find your device in the list of available target devices, request a custom Pattern Set. To do this, contact our Support Team.

  5. To upload the custom pattern set you received, navigate to Telnet Control > Pattern Sets, browse for the file and click Upload.

  6. To delete a custom Pattern Set from One Identity Safeguard for Privileged Sessions (SPS), click in the respective row. Generic Pattern Sets cannot be deleted.

Related Documents