-
Title
Compatibility of SPP and SPS versions -
Description
What versions of Safeguard for Privileged Passwords (SPP) and Safeguard for Privileged Sessions (SPS) are compatible?
Can Long Term Support (LTS) and Feature release versions of SPP and SPS be mixed and connected together?
-
Resolution
When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP major and minor versions match exactly. More details are below.Versions need to be synchronized during an upgrade.For example, it is expected that SPS version 6.6 can be joined to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.
It is not supported to mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0.7 to an SPP version 6.7.
It is also not supported to have mixed versions in a cluster or HA pair, this will not work.
At times a 'patch' release may be issued that is specific to SPP or SPS.
Feature Patch Release Methodology.
7.5.1
LTS Patch Release Methodology.
7.0.5.1
Feature Release Patch Compatability.Clusters and Pairs still need to be on the same complete version, For example a SPP cluster has to be on 7.5.1 if patched.
A SPP Cluster will work on 7.5.1 if joined to a SPS Cluster on version 7.5. This is because the major and minor release numbers match.
LTS Release Patch Compatability.
The same rules apply here except the version methodology is slightly different.
CClusters and Pairs need to be on the same complete version, for example a SPP Cluster has to be on 7.0.5.1 if patched.
A SPP Cluster will work on 7.0.5.1 if joined to a SPS Cluster on version 7.0.5.