Running Keeper SSO Connect as a Service on Linux
Setting up 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. 1.
    If the application is still running because you configured it with the web interface, stop the running instance on the command line by entering CTRL-C.
  2. 2.
    As the root user, create a system startup file /etc/systemd/system/ssoconnect.service with the following content (replace /path/to/keeper with your exact path and replace <user> with your username that will be running the process
1
[Unit]
2
Description=SSO Connect Java Daemon
3
4
[Service]
5
WorkingDirectory=/path/to/keeper (i.e. /home/keeperservice/sso_connect)
6
User=<user> (i.e. root)
7
ExecStartPre=/bin/sleep 10
8
ExecStart=/usr/bin/java -jar /path/to/keeper/SSOConnect.jar
9
10
[Install]
11
WantedBy=multi-user.target
Copied!
"chmod" the file:
1
sudo chmod 644 /etc/systemd/system/ssoconnect.service
Copied!
Enable the service to auto-start.
1
sudo systemctl enable ssoconnect.service
Copied!
Run systemctl to start the service.
1
$ systemctl start ssoconnect
2
$ systemctl status ssoconnect
Copied!

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:
1
http://127.0.0.1:9000/ping
Copied!
Note the local ping is being used here because we connected to the local instance via port forward. To check the service running from the outside (external users) you can use the public port:
1
$ curl "https://<public_ip_or_dns>:<port>/ping"
Copied!
Example request/response:
1
curl "https://sso.acme-demo.com:8443/ping"
2
3
{"configuration":"Running","sync_revision":41838,"sync":"Thu Nov 21 07:36:51 UTC 2019","version":"o14.1.2.4","sso":"Running","status":"Ready"}
Copied!
You can review log files which are located by default in /path/to/keeper/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.
1
$ tail -f /path/to/keeper/logs/ssoconnect.log
Copied!
The next section provides Identity Provider setup instructions for each major vendor.
Last modified 1yr ago
Export as PDF
Copy link