- This line was added.
- This line was removed.
- Formatting was changed.
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
While Redhat 7 / Centos 7 are still being supported, it is possible to continue using those operating system. Before their end of support, in June 2024, we recommend updating the operating system to Redhat 8 / Rocky Linux 8. Both series of operating system have been release tested again this IDS 2023.1 release. (SSO 9.2 and CustomerID 6.2).
|Linux distributions||CentOS||7||June 2024|
|Rocky Linux||8||May 2029|
|RedHat Enterprise Linux||7||June 2024|
|RedHat Enterprise Linux||8||May 2029|
|Microsoft Windows||Windows Server||2016||January 2027|
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 or 11 is required in order to run Ubisecure applications, including SSO, CustomerID and related components. Identity Server has been tested with the following Java builds. Releases from IDS 2022.1 (SSO 9.x.x and CustomerID 6.x.x) and later require a Java11 installation.
|8.x.x||5.x.x||Adoptium||Java 8 (1.8.0_312)|
|Oracle Corporation||Java 8 (1.8.0_312)|
|6.x.x||Adoptium||Java 11 (11.0.14)|
|Oracle Corporation||Java 11 (11.0.14)|
While we do support Centos 7, unfortunately, RedHat OpenJDK does not support an extensive amount of ciphers. Due to this limitation, we have not tested and therefore cannot recommend using RedHat OpenJDK. Please ensure you use one of the supported versions of Java shown above.
There are known issues with Ubisecure CustomerID with JRE 11.0.15 and later and these JRE versions should not be used in production as those might cause CustomerID not to start. Ubisecure is working to address this issue when a fix is available for Wildfly. Related issues:
Ubisecure Directory requires an LDAP implementation. Identity Server supports the following LDAP implementations
|OpenLDAP||2.5.16||Included in the SSO Linux distribution package. The used database backend is Memory-Mapped Database (MDB)|
|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
|PostgreSQL||12||9.6 → 12||November 2024|
|PostgreSQL||14||12 → 14||November 2026|
We have completed testing of PostgreSQL 14.6 with IDS 2023.1 patch releases. This offers support for installations through November 2026. If you have any concerns, please open a ticket with support. We will be happy to review your environment and ensure that it will continue to operation smoothly.
Note: PostgreSQL 9.6 is no longer recommended for use with any SSO 9.x.x or CID 6.x.x release versions.
Ubisecure recommends using PostgreSQL 14. PostgreSQL 9.6 has been tested with CustomerID and Accounting found in IDS 2021.3 release, but as PostgreSQL 9.6 is now EOL, we encourage customers to upgrade their database.
Currently tested PostgreSQL JDBC driver version is 42.6.0
For upgrading PostgreSQL from 9.6 to 12, follow PostgreSQL official documentation for upgrading with pg_dumpall (https://www.postgresql.org/docs/12/upgrading.html). We have created Knowledge Base "How-to" article with information how we have tested the upgrade and also include estimated migration times. See Upgrade and migrate to new version of PostgreSQL
In high-performance deployments Ubisecure Identity Server uses Redis as a session storage. Identity Server has been tested with version 6.2.8. 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.
Note that while using Ubisecure Directory (OpenLDAP) on Linux you need to make sure that the storage allocation is sufficient to handle the expected increase of identities. If the identities in the system go above allocated storage, the system will stop working.
Make sure that you chose a proper
Also note that
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)|
|1 000 000||8.0||2.4|
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|
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.
|For optimal performance of Ubisecure Directory (OpenLDAP) on Linux it is recommended that the system has at least the amount of RAM that can fit the max size of the user data storage as described above in the Storage section|
|Application||Recommended amount of RAM (GB)|
|Ubisecure Directory (OpenLDAP) Linux||8|
|Ubisecure Directory Windows||1|
For more information on memory configurations, please refer to
- CustomerID: Wildfly JVM settings reference
- SSO: Tomcat memory considerations
- PostgreSQL: PostgreSQL resource consumption
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.
|Table of Contents|