Linux Command-line Configuration
Configuration on Linux without a GUI
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
- 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):
<your slot>(required for Gemalto, often 0 or 1)
********(required for Gemalto, this is the Crypto Officer password on the HSM)
- Certificate chain file (/home/ubuntu/keeperSSO/data/sso_keystore.jks):
- 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.
SSO Connect will not automatically start after a configuration session so you need to start it:
$ java -jar SSOConnect.jar
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\]\]\[...\]
SSOConnect can also be configured via the following command line switches.
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 [email protected] -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.