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.
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.
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
"chmod" the file:
Enable the service to auto-start.
Run systemctl to start the service.
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:
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:
Example request/response:
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.
The next section provides Identity Provider setup instructions for each major vendor.