This page includes useful information for the consideration of an environment specification and system recommendation for running Ubisecure Identity Server. Below you will find the currently supported software, actively tested browsers and hardware requirements and recommendations. All recommendations are based on an example reference environment of 100 000 active users with 100 logins per second as normal sustainable, non-impacting load.
These are not intended to highlight the minimum requirements but instead Ubisecure's recommendations in order to effectively run the Identity Server in a production environment. Ubisecure performs release testing on a variety of environments for each release, using a combination of single and dual-node installations on Linux and Windows Server operating systems and with automated and manual regression testing performed by a variety of the listed supported browsers in their latest stable distribution.
Your exact environment needs may need to be reviewed and altered depending on what types of workloads you run. Your workload is influenced for example by these factors (but not limited to):
- Active users having user account in Ubisecure Directory and CustomerID database
- Number of internal and external authentications
- Number of requests to Identity Server APIs
- Number of interactions with CustomerID registration flows and Self-Service UI
Ubisecure Identity Server has been tested with the following desktop browsers
- Google Chrome
- Mozilla Firefox
- Microsoft Edge
Ubisecure recommends to use the latest version of each browser
Supported Operating Systems
Ubisecure Identity Server supports a number of Linux distributions and Microsoft Windows Server.
|RedHat Enterprise Linux||7|
|Microsoft Windows||Windows Server||2016, 2019|
The following chapter lists the required software that is used to run Ubisecure Identity Server. Ubisecure lists the software that it uses internally to develop, test and operate Identity Server.
Java 8 is required in order to run Ubisecure applications, including SSO, CustomerID and related components. Identity Server has been tested with the following Java builds
A JDK issue prevents RedHat builds of OpenJDK to be used with Ubisecure Identity Server.
Ubisecure Directory requires an LDAP implementation. Identity Server supports the following LDAP implementations
|OpenLDAP||2.4.44||Included in the SSO Linux distribution package. The used database backend is currently BerkeleyDB (bdb)|
|Microsoft AD-LDS||Windows Server 2016, Windows Server 2019||Tested with the version included in the respective Microsoft Windows Server version|
CustomerID and Accounting support the following Relational Databases
Ubisecure highly recommend using these versions of PostgreSQL as these are used in testing and development. Newer versions of PostgreSQL may work as well but are not recommended as Ubisecure has not tested any other version than the ones listed here.
PostgreSQL JDBC Driver
Currently tested PostgreSQL JDBC driver version is 42.2.5
In high-performance deployments Ubisecure Identity Server uses Redis as a session storage. Identity Server has been tested with version 5.0.5. Fore more information, please refer to Use Redis with Identity Server.
These hardware recommendations can easily sustain a deployment with 100 000 active users and 100 logins per second.
Ubisecure recommends always deploying a reverse proxy or load balancer in front of any operational environment. This is useful for security and traffic management of any internet facing environment.
Ubisecure Identity Server uses two persistent data stores for storing identity related information; PostgreSQL and LDAP. The necessary storage size largely depends on the number of users, roles, organisations and custom attributes stored in the Ubisecure Identity Server.
The following table lists the actual size of data on disk for a typical deployment storing users in 100 different organisations, including 5 roles for each organisation and 5 custom attributes for each user:
|Number of user accounts||Ubisecure Directory size (GB)||CustomerID database size (GB)|
On average, each LDAP user account entry takes roughly a bit less than 10 kB whereas CustomerID database entry takes roughly 3 kB. Deployments that do not use Redis as a session storage, an additional 10 kB per single-sign-on session should be considered. The single-sign-on sessions are stored in Ubisecure Directory.
Accounting login events
In addition to identity data, as of IDS 2019.1 login events are collected into the Accounting Service database. The following table lists the actual size of data on disk for a system which contains roughly 100 000 monthly active users each able to select any of 10 configured authentication methods.
|Number of login events||Accounting database size (GB)|
|1 000 000||1.0|
|5 000 000||4.0|
|10 000 000||8.0|
Configure login event data cleanup
It is highly recommended to configure the cleanup of old login event related data. See Accounting Service additional configuration for more details.
|SSO and Accounting*||2|
*) Currently Accounting is installed alongside SSO thus the processes share the same resources.
For running the Identity Server applications, the following table lists the memory recommendations.
|Application||Recommended amount of RAM (GB)|
For more information on memory configurations, please refer to
Redis memory considerations
When deploying Redis with Ubisecure Identity Server each single-sign-on session takes maximum of 10 kB of memory in Redis. In a typical Redis deployment (3 primary instances backed up by 3 secondary instances) this would mean
|Number of concurrent sessions||Number of Redis primary instances||Memory required per Redis instance (GB)|
|1 000 000||3||6.67|
Note that the sessions are sharded between the three primary instances. For more information, please refer to How to use Redis with Identity Server.