Install Keeper SSO Connect

Last updated 2 days ago


1. Download the Keeper SSO Connect application from the Admin Console and stage the executable on the server.

2. . Install Java 8 if not currently installed

NOTE: Java 9 is not compatible.

3. Reboot the server

Installation - Windows

1. Extract the Keeper SSO Connect app.

2. Run KeeperSSOConnect as administrator.

3. Upon successful completion of the new installation the app will launch a web browser. (We recommend using Google Chrome to perform the initial setup). If the configuration web page doesn’t launch you can launch it with the new SSO Connect Icon on the desktop.

If you receive an error connecting to the Keeper SSO Connect service, you need to reboot the server. Also, you need to ensure that your web browser is able to connect to over port 443. Keeper SSO Connect does not support the use of proxy servers or firewalls that perform SSL packet inspection.

Installation - Linux

Instance Requirements

  1. Java 8 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 Java 8 is installed and in your path. Java 9 and Java 7 are NOT supported.

  • $ java -version

Create a dedicated folder to host the SSO Connect application:

  • $ mkdir sso_connect

Download the latest Keeper SSO Connect / 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 begin the configuration 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 web GUI via SSH Tunnel

To remotely configure SSO Connect through the web interface, simply open an SSH tunnel to the target system, for example:

  • $ ssh -L 9000: ec2-user@

Then open your web browser on your local system to:


Option 3: Configure through SSH / command line options

Keeper SSO Connect can be start up in a configuration mode which prompts you for the necessary parameters.

  1. From the remote instance that is currently running Keeper SSO Connect, stop the existing running SSO instance by hitting CTRL-C or kill the process.

  2. Copy the SSL Certificate (PKCS#12 or Java Keystore, IdP XML Metadata file) to the server

  3. In the SSO Connect directory start the service in "config mode"

    • $ java -jar SSOConnect.jar -c

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

  • Keeper email address (of Admin)

  • Keeper Master Password (of Admin)

  • Two-Factor code (if enabled on account)

  • SSO Domain Name (this comes from the Admin Console provisioning screen)

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

  • SSO Connect Hostname or IP Address

  • Advertised SSL Port

  • Bound (private) IP

  • Bound (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

One the settings have been successfully implemented, they will sync to all other SSO Connect services upon restart of the service on each instance.

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

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

* -initialize


SSO name to initialize the instance to.

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)

* -sso_ssl_port


Public / advertised SSO Connect port

* -private_ip


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

* -private_port


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

* -key_store_type


Either jks or p12



Password for the keystore

* -key_password


Password for each key in the keystore

* -ssl_file


Location of the ssl file to convert

* -saml_file


Location of the saml file

* -sign_idp_traffic


True if all incoming and outgoing traffic are signed

* -idp_type


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

* -map_first_name


Field the IDP sends the user's first name as

* -map_last_name


Field the IDP sends the user's last name as

* -map_email


Field the IDP sends the user's email as

* -admin_port


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. Create a system startup file /etc/systemd/system/ssoconnect.service with the following content:

  • [Unit] Description= SSO Connect Java Daemon [Service] WorkingDirectory=/home/{user}/sso_connect User={user} ExecStart=/usr/bin/nohup /usr/bin/java -jar /home/{user}/sso_connect/SSOConnect.jar /home/{user}/sso_connect

  • ### On Centos/RedHat you may need "nohup" in ExecStart. [Install]

3. Run systemctl to start the service

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

Troubleshooting Linux

  1. 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>:<port>/ping

2. 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 to put your log files anywhere you wish.

Protection of Data Files

In the SSO Connect installation folder is a data/ directory. Inside the data directory there are 3 files. Two of the files contain secret keys generated on the server that must be protected and are utilized to encrypt and decrypt the end-user's auto-generated master passwords. There is also a .sql file which contains a local cache of encrypted data. It is critical that access to this data folder is restricted.

Windows GUI Configuration

Log into the SSO Connect Web UI with a Keeper Administrator account.

  • This account should not be configured for Single Sign-On.

Enter Two Factor Authentication code if prompted.

Select the SSO Connection (Enterprise Domain).

Once you successfully authenticate Keeper SSO Connect to your Admin Console you will see the status tab:

Select on the Configuration link to begin the setup.

Enter the Advertised Hostname or IP Address. This address is what the Keeper client applications navigate to in order to initiate the SSO authentication process. If installing Keeper SSO Connect in an HA (High Availability) configuration, this is the address the that points to the load balancer. This address can be either an IP or a hostname. Bound IP Address. This is the physical IP address of the NIC on the server. If a hostname is not used and if there is only one address associated with the server this entry will be the same as the Hostname or IP Address field. In the is the Advertised Hostname that gets routed to the local address The Keeper SSO Connect service binds to the Private IP address.

  • The IP/Hostname must be accessible by users who will be accessing Keeper. You may need to update your firewall to allow access over the IP and port.

SSO Connect SSL Key and Certificate

In order for the Keeper SSO Connect service to start an SSL Certificate is required. A self signed certificate can be generated. However, before deploying to production, it is recommended that a proper SSL Certificate from your certificate authority be generated and uploaded to this section. Self-signed certificates will generate security errors for your users on many browsers. The certificate file type need to be either .pfx or .p12 for a PKCS 12 certificate or a .jks for a Java Key Store certificate. Most CA's have instructions on their sites on how to convert to these file type if they did not initially issue these specific formats.

  • Note: SSL Certificates must be renewed yearly

Select your specific IDP. If your IDP is not in the pull down select Default.

SSO Connect Status

Reasons your status is listed as Stopped:

1. Your SSL Certificate is missing or incorrect.

  • The hostname in the SSL certificate doesn’t match the hostname in SSO Connect. **A wildcard SSL cert can be used or one created for the specific hostname. (i.e. if your hostname is your cert should be set up for *

  • By default the Use Certificate to Decrypt and Sign SAML Response/Request should be selected.

** See Appendix on creating a self-signed SSL cert if you need to create a self signed SSL certificate for testing or troubleshooting your SSL certificate.

IdP Metadata

Select your IdP Provider. If your provider is not listed select Default. The next step is to upload the IdP metadata file. This file can be downloaded from your IdP.

Identity Provider Attribute Mappings

Attribute Mappings do not require any changes. Select Save.

Restarting the Keeper SSO Connect Service on Windows

The Keeper SSO Connect runs as a service on Windows. Closing out the web interface does not stop the service. The service can be stopped and started from the Service MMC in windows.