A minimum of the following system prerequisites must be fulfilled for installation of the application server.
|
Requirement |
Detail |
|---|---|
|
Processor |
8 physical cores 2.5 GHz+ |
|
Memory |
8 GB RAM |
|
Hard drive storage |
40 GB |
|
Operating system |
Windows operating systems The following versions are supported:
Linux operating systems
|
|
Additional software |
Windows operating systems
Linux operating system
|
This section lists the data systems supported by One Identity Manager connectors in this version.
|
Connector |
Supported data systems |
|---|---|
|
Connectors for delimited text files |
Any delimited text files. |
|
Connector for relational databases |
Any relational databases supporting ADO.NET. NOTE: Additional installation of an ADO.NET data provider from a third party may be necessary. Ask Microsoft or the relational database producer. |
|
Generic LDAP connector |
Any LDAP directory server conforming to version 3. The LDAP connector requires the directory server to be RFC conform. Specifically, to conform to the standards RFC 4514 (Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names) and RFC 4512 (Lightweight Directory Access Protocol (LDAP): Directory Information Models). NOTE: Other schema and provisioning process adjustments can be made depending on the schema. |
|
Active Directory connector |
Active Directory shipped with Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019,Windows Server 2022, and Windows Server 2025. |
|
Microsoft Exchange connector |
|
|
SharePoint connector |
|
|
SAP R/3 connector |
|
|
Unix connector |
Supports the most common Unix and Linux derivatives. For more information, see the specifications for One Identity Authentication Services. |
|
Domino connector |
The same major version is used for the HCL Domino Server and the HCL Notes Client. |
|
Generic database connector |
|
|
Mainframe connector |
|
|
PowerShell connector |
|
|
Active Roles connector |
|
|
Microsoft Entra ID connector |
|
|
SCIM connector |
Cloud applications, which recognize the System for Cross-domain Identity Management (SCIM) specification in version 2.0. They must conform to RCF 7643 (System for Cross-domain Identity Management: Core Schema) and RFC 7644 (System for Cross-domain Identity Management: Protocol). |
|
Exchange Online connector |
|
|
Google Workspace connector |
|
|
Oracle E-Business Suite connector |
|
|
SharePoint Online connector |
|
|
One Identity Safeguard connector |
You can find the PowerShell module to match each supported version in the Modules\PAG\dvd\AddOn\safeguard-ps directory on the One Identity Manager installation medium. Versions without a matching PowerShell module on the One Identity Manager installation medium are not supported. |
You can choose between two paths for receiving releases: Long Term Support (LTS) Release or Feature Release.
Long Term Support (LTS)
The initial One Identity Manager LTS release is 9.0. For all LTS releases of One Identity Manager, the first digit identifies the release and the second is always a zero (for example, 9.0).
Maintenance LTS Releases (known as Cumulative Updates): A third digit is added; for example, 9.0.1.
Feature Release
Feature Releases' version numbers are two digits (for example, 9.1, 9.2, 9.3 etc).
The table below shows a comparison of Long Term Support (LTS) Release and Feature Release.
|
Category |
Long Term Support (LTS) Release |
Feature Release |
|---|---|---|
|
Release frequency |
Every 36 months (includes resolved issues and security related updates). |
Approximately every 12 months (includes resolved issues and security related updates). |
|
Duration of full support |
36 months |
18 months |
|
Duration of limited support |
12 months (after the end of full support) |
6 months (after the end of full support) |
|
Versioning |
All versions where the second number is 0. For example: 9.0.0 (9.0.1, 9.0.2,), 10.0.0, 11.0.0, and so on. |
All versions where the second number is not 0. For example: 9.1.0 (9.1.1, 9.1.2), 9.2, 9.3, and so on. |
|
Duration of service pack availability between releases |
Approximately every 6 months, cumulative updates (CUs) are expected for each LTS release. |
Every 6 months patch releases (service pack) are expected for each feature release currently supported. |
|
Criteria for issuing hotfixes for LTS outside of a cumulative update cycle |
|
|
Release details can be found at Product Life Cycle.
One Identity strongly recommends always installing the latest revision of the release path chosen by the customers/partners (Long Term Support path or Feature Release path).
You can move from an LTS version (for example, 9.0 LTS) by installing a later feature release or version (for example 9.3). Once this has happened, you are not on the LTS support path until the next LTS base version (10.0, etc.) is installed.
You can move from a Feature Release to an LTS Release, but only to an LTS release with a later version. For example, you cannot move from 9.3 to 9.0 LTS. You have to keep upgrading with each new Feature Release until the next LTS Release version is published. For this example, you would wait until 10.0 LTS is available.
For LTS, there are no patches released, only hotfixes, and these are distributed only in rare cases. Refer to the previous table to see the criteria for LTS hotfixes. These hotfixes need to be applied in order of their release.
LTS has periodic cumulative updates (CUs) provided for LTS customers, which roll out the issues resolved during that period. It is not required to install every CU separately. For instance, if CU1 is released followed by CU 2, you do not need to install CU1 before installing CU2. The CUs are cumulative.
For more information, see the knowledge article 4372133.
For customers on the feature release option track, maintenance releases are cumulative, meaning that maintenance releases do not need intermediate releases to be installed to update to a newer maintenance release. This is unchanged from previous versions. For example, if you want currently use version 9.1.1 and want to upgrade to 9.3, and, for example, versions 9.1.3, 9.1.4, and 9.1.5 have been released, you only have to install version 9.3 and it automatically applies the resolved issues from 9.1.3, 9.1.4, and 9.1.5.
What is Long Term Support (LTS)?
LTS is a support option that allows you to stay on the same release for an extended period of time while still receiving the high level of support that One Identity is known for. While on the LTS path, you receive updates aimed at resolving issues and vulnerabilities. There are not, however, any product enhancements or features delivered while on the LTS release.
What are the benefits to being on an LTS release?
Some enterprises have a difficult time in keeping up with the migration to new releases in a timely manner to fit within the vendor’s support guidelines. This allows the enterprise to stay on one version for a considerable amount of time.
What are the disadvantages to being on an LTS release?
The negatives, of course, are missing out on receiving the latest enhancements and features from the vendor.
Duration of an LTS release
A Long Term Support (LTS) version provides you with up to 3 years of support after the original release date or until the next LTS release (which ever date is later); with an option to continue via Extended Security Support (ESS).
How do I make the move to the LTS support option?
When you install an LTS version, such as One Identity Manager 9.0, you are automatically on the LTS path. The choice you make for the next release that you install, determines whether you remain on LTS or go to the traditional support model.
Once I choose to go on the LTS path, can I ever move back to the feature release path?
Yes. You can do this by installing a later maintenance version or feature release. For example, if you currently have version 9.0 (LTS) and decide to move to 9.3, you will come off the LTS support path until you install the next base LTS version (10.0, etc.)
Is there an extra charge if I choose the LTS option?
No, long term support is included in your annual maintenance renewal. An option to continue limited support is offered at an additional charge via our Extended Security Support (ESS).
Use of this software is governed by the Software Transaction Agreement found at https://www.oneidentity.com/legal/sta.aspx. This software does not require an activation or license key to operate.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
