Installation - Linux

Installation - Linux

Instance Requirements

  1. Java 1.8 or Java 11 runtime environment.

  2. Inbound port required for SAML communication from end-user device/browser (defaults to port 8443). If users can login from IdP on the public Internet, then this port must be public.

  3. Outbound SSL port 443 opened to

  4. SSL private key (PKCS#12 or Java Keystore). During initial testing, a self-signed certificate is sufficient but users will receive a browser security warning.

  5. FQDN assigned to the instance or to the load balancer.

  6. SAML 2.0 compatible IdP.

Initial installation of Keeper SSO Connect can be performed on a single instance prior to being deployed in an HA environment. After the service is configured, the settings will automatically synchronize between load balanced instances. Make sure that the correct version of Java is installed and in your path. Java 1.7, Java 9, and Java 10 are NOT supported.

$ java -version

Create a dedicated folder to host the SSO Connect application:

$ mkdir sso_connect

Download the latest Keeper SSO Connect for Linux version from this link:

$ cd sso_connect
$ wget
$ unzip

Then start the Keeper SSO Connect service:

$ java -jar SSOConnect.jar

Now that the application is installed, you can configure SSO using the web browser GUI or through the command line. Configuration options are discussed next.

Option 1: Configure through web GUI with local port access

By default, the configuration port of Keeper SSO Connect is port 8080. If you have local access to the target system, just open your web browser to:

Option 2: Configure through the web GUI via an SSH Tunnel

To remotely configure SSO Connect through the web interface, simply open an SSH tunnel to the target system, for example: If you do not have direct browser access to the SSO Connect machine, you may be able to configure a tunnel to the machine:

$ ssh -L 9000: ec2-user@

Then open your web browser on your local system to:

Option 3: Configure SSO Connect with interactive mode

Keeper SSO Connect can be started in configuration mode, which prompts you for the necessary parameters.

  1. Stop the running SSOConnect process, if any, by hitting CTRL-C or killing the process.

  2. Copy the SSL Certificate to the SSO Connect server. It must be in PKCS#12 or Java Keystore format, meaning a file ending with .pfx, .p12, or .jks.

  3. Copy the IdP's SAML XML Metadata file to the server.

    • This is obtained from your IDP admin site (Active Directory, Azure, F5, Google, Okta, etc.).

    • This is usually an .xml file.

  4. In the SSO Connect directory start SSO Connect in configuration mode: $ java -jar SSOConnect.jar -config

  5. You will be prompted to supply the following parameters:

  6. Keeper Administrator email address (to login to the Keeper Admin Console for your company)

  7. Keeper Administrator Master Password

  8. Two-Factor code (if enabled on account)

  9. SSO Domain Name (this attribute is defined on the SSO Connect provisioning screen on the Keeper Admin Console)

    • Note that each Domain configured in Keeper will require a separate SSO Connect installation.

Next you will be able to configure each individual parameter. Leave the setting blank (hit <Enter>) to accept the default setting.

  • SSO Connect External Hostname or IP Address

  • External SSL Port (default = 8443)

  • Local (private) IP

  • Local (private) Port

  • Use Certificates to decrypt and sign the saml response and requests (True/False)

  • SAML Attribute mapping for "First Name"

  • SAML Attribute mapping for "Last Name"

  • SAML Attribute mapping for "Email"

  • IdP Type (Google, Okta, Azure, etc...)

  • Key Store Password (if using Java Keystore)

  • PKCS#12 Passphrase (if using SSL Key)

  • Full path and name of Key File

  • Full path and name of IdP SAML Metadata file

The following questions relate to using an HSM (Hardware Security Module) for secure key storage. If you do not have an HSM or do not want SSO Connect to use one you can skip this section.

  • Configure Secure Key Storage (y/N):

  • Type of Secure Key Storage (Gemalto SafeNet Luna HSM): Enter (AWS Cavium CloudHsmV2 is also supported)

  • Secure storage device access parameters (slot,password): Enter

  • slot: <your slot> (required for Gemalto, often 0 or 1)

  • password: ******** (required for Gemalto, this is the Crypto Officer password on the HSM)

  • Certificate chain file (/home/ubuntu/keeperSSO/data/sso_keystore.jks): Enter (required)

  • Certificate chain file password (none):

  • Enable Secure Key Storage (Y/n):

Once the settings have been successfully implemented, they will sync to all other SSO Connect services upon restart of the service on each instance. Once the settings are sufficient for SSO Connect to start up and contact the Keeper server, the settings will sync to all other SSO Connect instances on the same domain when they are restarted.

Note: JKS Keystore type may require both Key Store and Passphrase to be the same

SSO Connect will not automatically start after a configuration session so you need to start it:

$ java -jar SSOConnect.jar

Option 4: Configure through SSH full command-line parameters

SSO Connect supports many command-line options that can be scripted to automate operations such as rotation of SSL keys.

For a full list of command line parameter options, use the "-h" flag:

$ java -jar SSOConnect.jar -h
Usage: java -jar path\_to\_jars/SSOConnect.jar \[option \[option\_argument\]\]\[option \[option\_argument\]\]\[...\]



-h or -help

Display this help text.

-c or -config

Configure SSOConnect via prompts.

-v or -version

Output the version.

-l or -list

Output the configuration to the console.

-d or -debug

Output the class path and other information to the console for trouble shooting.

-s or -sync

Performs a full sync. System must already be initialized.

SSOConnect can also be configured via the following command line switches.






Username of admin who can configure this instance of SSO Connect



Keeper Master Password



Two factor token



SSO name to initialize the instance to.



turn on Secure Key Storage (e.g. a Hardware Security Module)



turn off Secure Key Storage (e.g. a Hardware Security Module)

Note: if the instance is already initialized, you cannot re-initialize without deleting the contents in the data directory






Export the SSOConnect Service Provider XML to the file name supplied as the argument. Instance must already be initialized.



Public / advertised FQDN (fully qualified domain name)



Public / advertised SSO Connect port



IP Address to bind ssl service to (if not supplied will default to the resolved ip of sso_connect_host)



Port to bind ssl service to (if not supplied use sso_ssl_port)



Either jks or p12



Password for the keystore



Password for each key in the keystore



The value can be “rsa” or “ec” (case-insensitive)



Location of the ssl file to convert



Location of the saml file



True if all incoming and outgoing traffic are signed



The number corresponding to the desired IDP: 0 Default, 1 F5 Networks BIG-IP, 2 Google, 3 Okta, 4 Microsoft ADFS, 5 Microsoft Azure, 6 OneLogin



Field the IDP sends the user's first name as



Field the IDP sends the user's last name as



Field the IDP sends the user's email as



Http port for the administrative configuration web server runs on. Note: this value is per instance. To disable the configuration web server for a given machine, simply set this to 0.

Command-line options require username, password, and two-factor values (if 2FA is enabled). Either set them as an option or you will be prompted for them.

For example, to rotate the SSL key of a running environment, the command will look something like this:

$ java -jar SSOConnect.jar -key_store_type p12 -key_store_password XXX -key_password XXX -ssl_file /path/to/sslfile -saml_file /path/to/samlfile -username -password masterpass -twofactor 123456

You will be prompted to supply passwords through the interactive shell if left unset.

After you configure an instance, the changes will be immediately pushed to all other SSO Connect instances in your HA environment.

SSOConnect will uses the standard log4j2 libraries as its logger. It will look for the configuration file in the following order:

  • Value of the system environment variable 'logging.config'

  • log4j2.xml in the current working directory

  • log4j2.xml in the directory the SSOConnect.jar file is in

  • a log4j2 configuration file according to the standard log4j2 search criteria

  • the default log4j2.xml included inside the SSOConnect.jar file

Modifying the log4j2.xml file will only take affect after the service is restarted and only if it is the first log4j2 configuration file found.

Running Keeper SSO Connect as a Service on Linux

Once your server is setup and operational you should setup SSO Connect as a service. This operation will vary depending on your OS.

  1. If the application is still running because you configured it with the web interface, stop the running instance by entering ctrl-c.

  2. As the root ueser, create a system startup file /etc/systemd/system/ssoconnect.service with the following content:

Description=SSO Connect Java Daemon
ExecStart=/usr/bin/java -jar /home/<user>/sso_connect/SSOConnect.jar /home/<user>/sso_connect

"Chmod" the file:

sudo chmod 644 /etc/systemd/system/ssoconnect.service

Run systemctl to start the service

$ systemctl status ssoconnect
$ systemctl start ssoconnect
$ systemctl status ssoconnect

Troubleshooting Linux

To test the service response or to monitor the health of the Keeper SSO Connect instances, you can query the "Ping URL" which in the above example is:

For most installations, this will be:

$ curl "https://<public_ip_or_dns>:<port>/ping"

Example request/response:

curl ""
{"configuration":"Running","sync_revision":41838,"sync":"Thu Nov 21 07:36:51 UTC 2019","version":"o14.1.2.4","sso":"Running","status":"Ready"}

You can review log files which are located by default in working_directory/logs/ssoconnect.log. The logging is done through a standard log4j2.xml file located in the install directory. You may change the log4j2.xml file to place your log files anywhere you wish.