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 One Identity Safeguard for Privileged Sessions (SPS). Such credentials include passwords and public keys. Local User Databases are most commonly used in inband gateway authentication scenarios.
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.
To create a Local User Database
Navigate to Policies > Local User Databases and click .
Enter the name of the Local User Database.
Click to add entries.
Figure 181: Policies > Local User Databases — Mapping keys
Enter the name of the user into the Username field.
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 field, and upload the public key 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).
Repeat the above steps to add other users as required.
Navigate to the Authentication Policies tab of the respective protocol and select the Local User Database there.