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

Creating a Local User Database

Purpose:

Local User Databases are available for HTTP, RDP, SSH and Telnet protocols, and can be used to authenticate the clients to credentials that are locally available on SPS. Such credentials include passwords, public keys, and certificates. Local User Databases are most commonly used in inband gateway authentication scenarios. To create a Local User Database, complete the following steps.

NOTE:

To store credentials on SPS and use them to authenticate on the server, use a local Credential Store. For details, see Using credential stores for server-side authentication.

Steps:
  1. Navigate to Policies > Local User Databases and click .

  2. Enter the name of the Local User Database.

  3. Click to add entries.

    Figure 156: Policies > Local User Databases — Mapping keys and certificates

  4. Enter the name of the user into the Username field.

    NOTE:

    If you also use Usermapping policies, enter the username that the client will use on the server side. If you also use gateway authentication, the gateway username can be used as well.

    • If you use public-key based authentication on the client side, click the icon in the Public Keys and Certificates > Public keys field, and upload the public key of the client.

    • If you use certificate-based authentication on the client side, click the icon in the Public keys and Certificates > Certificates field, and upload the certificate of the client.

    SPS will verify that a client trying to use the username set in Step 3 is authenticating itself with the private key that corresponds to the uploaded public key or certificate.

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

  5. Repeat the above steps to add other users as required.

  6. Click Commit.

  7. Navigate to the Authentication Policies tab of the respective protocol and select the Local User Database there.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating