The Keeper SSO Connect is a lightweight service that can be installed on a private on-premise or cloud-based server. The application is hosted by the customer in order to preserve zero knowledge and provide compatibility with any SAML 2.0 compatible identity provider.
The following server platforms are currently supported.
Supported Windows Server versions Windows Server 2008 R2 Datacenter SP1 64-bit Windows Server 2008 R2 Enterprise Windows Server 2012 R2 Standard Windows Server 2012 R2 Datacenter Windows Server 2016 Datacenter Windows Server 2016 Standard Windows Server 2019 Standard Windows Server 2019 Datacenter
Supported Linux versions: Ubuntu 18+ CentOS 7+ Debian 9.8+ openSUSE Tumbleweed openSUSE Leap 15.1+ Red Hat Enterprise Linux 6.8+
Supported Java versions 1.8.0_202-b08 1.8.0_212-b10 1.8.0_221-b11 1.8.0_231-b11 Java 11.0.5 (LTS) Java SE 11.0
Keeper SSO Connect requires Java JRE or JDK running on the server. We recommend customers use Java 11.0 (LTS). If you have a different version of Java installed we recommend uninstalling that version and install Java 11.0 first before you proceed. Otherwise you may experience service hanging during installation.
To ensure all Java installation dependencies are met we require that you install Java using the appropriate .exe or .msi installer which will setup the environment as needed to operate correctly.
We recommend installing OpenJDK 11.0 which can be downloaded from the link below: https://github.com/ojdkbuild/ojdkbuild/releases/download/java-11-openjdk-126.96.36.199-2/java-11-openjdk-jre-188.8.131.52-2.windows.ojdkbuild.x86_64.msi
We also support Oracle Java SE 11.0 which can be downloaded from here: https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
The following table outlines the minimum hardware requirements per each server.
Max # of users per server
Processor speed (GHz)
Number of processors / Cores
1 / 4
1,000 - 50,000
2 / 4
50,000 - 100,000
2 / 8
The Keeper Connect service on a single instance can handle thousands of simultaneous users.
However, both scalability and high availability can be achieved by placing a load balancer in front of a cluster of Keeper SSO Connect servers. The Keeper Cloud backend will take care of configuration synchronization. Changes applied to one server are automatically distributed to all servers in the same SSO node cluster. This includes the user database.
Further scalability, for example to scale to 100,000 users or more, can be achieved by splitting groups of users up into multiple SSO Connect domains. This will require creating separate SSO-enabled node(s) in the Keeper Admin Console and a separate SSO server or server cluster for each node.
SSO Connect can optionally be integrated with Amazon CloudHSM or Gemalto HSM solutions to protect the private encryption keys. The following HSM modules are currently supported:
Linux or Windows servers are supported.
Currently only Linux-based SSO Connect instances supported.
The following network requirements apply to Keeper SSO Connect deployments.
Keeper SSO Connect network connections to Keeper Cloud servers at keepersecurity.com (US) or keepersecurity.eu (EU customers) is TCP/443 (TLS 1.2) outbound stateful.
End-user devices must connect to SSO Connect via the advertised public FQDN/IP and TCP port. For example, keepersso.mycompany.com.
Local server bind port and the external advertised connection port are configurable separately. In that scenario the ports need to be translated via a load balancer, firewall or locally (eg. iptables).
The external advertised TCP port that is configured in SSO Connect (default TCP/8443) needs to be allowed inbound into the network subnet where the SSO Connect servers are located. For example if the service is running on Windows, use Windows Firewall to open the port to SSO Connect. 8443 is just the default, you can use any port.