The following describes how to store the public keys of the users and the private-public keypair used in the server-side connection locally on One Identity Safeguard for Privileged Sessions (SPS).
To configure public-key authentication using local keys
-
Navigate to Policies > Local User Databases and create a Local User Database. Add the users and their public keys to the database. SPS will authenticate the clients to this database. For details on creating and maintaining local user databases, see Creating a Local User Database.
-
Navigate to Policies > Credential Stores and create a Local Credential Store. Add hostnames and the users to the database. SPS will use these credentials to authenticate on the target server. For details on creating local credential stores, see Configuring local Credential Stores.
-
Navigate to Traffic Controls > SSH > Authentication Policies and create a new Authentication Policy.
-
Select Authenticate the client to SPS using > Local > Public key, clear all other options.
-
Select the appropriate usergroup from the Local User Database field. SPS will authenticate the users to this local database.
-
Select Relayed authentication methods > Public key > Fix, clear all other options.
-
Click
> Generate. This will generate a private key that is needed only for the configuration, it will not be used in any connection.
NOTE: 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.
-
Click
.
-
Navigate to Traffic Controls > SSH > Connections and create a new Connection.
-
Enter the IP addresses of the clients and the servers into the From and To fields.
-
Select the authentication policy created in Step 1 in the Authentication Policy field.
-
Configure the other options of the connection as necessary.
-
Click
-
To test the above settings, initiate a connection from the client machine to the server.