I’m with others on this being confusing. (Dates are inconsistent) and how we can test in Sandbox environments and also in Production tenants prior to sources disconnecting / failing. Can this article please be updated with consistent dates and testing procedures for sandbox and production tenants? I’m still confused on whether this needs to happen by April 10 to avoid failures in Production or whether its April 28th
Hi Gupta,
I just wanted to clarify the dates mentioned. You mentioned that the temporary compatibility support is available until April 10, and that the Sandbox release is scheduled for April 14.
Based on this, I wanted to confirm whether this change will be applied automatically as part of the release???
If that is the case, then after April 14, as part of our validation, we can proceed with:
-
Performing a health check (Test Connection), and
-
Running Discovery (account and entitlement aggregation).
Through these validation steps, if we identify any target/source systems failing due to TLS issues, we can then work with the respective application teams to upgrade or remediate their certificates as required.
Please let us know if our understanding is correct.
Hi Team,
We validated TLS settings on three servers as part of the SHA‑1 deprecation update. Please confirm which of these will be impacted:
Server 1
-
Protocol: TLS 1.3
-
Cipher: TLS_AES_256_GCM_SHA384
Our understanding: Not impacted (modern TLS 1.3)
Server 2
-
Protocol: TLS 1.2
-
Cipher: ECDHE-RSA-AES256-SHA384
Our understanding: Not impacted (SHA‑384, forward secrecy)
Server 3
-
Protocol: TLS 1.2
-
Cipher: AES128-SHA
Our understanding: Impacted — uses SHA‑1 and will fail once SHA‑1 handshake signatures are fully disabled.
Please confirm if this assessment is correct.
Thank you.
Could I kindly ask you what is the updated timeline for these changes?
Is the Sandbox release date of 14th of April still valid? So the postponed released (to July) is only relevant for the production environments?
Thank you!
@samgupta /Sailpoint team - can someone confirm if this change is deployed to Sandbox environments (previously mentioned date was 04/14/2026).
Thanks,