For the complete documentation index, see llms.txt. This page is also available as Markdown.

SSO Connect On-Prem 17.1.2

Released June 26, 2026

This release delivers critical security remediation for SAML authentication bypass vulnerabilities, hardens the administrative interface against unauthorized access, and removes unnecessary dependencies to reduce the attack surface. No configuration changes are required for administrators.

What’s New

  • Strengthened SAML signature validation to bind cryptographic verification to the assertion it covers, closing a signature relocation bypass that survived the 17.1.1 fix.

  • Hardened administrative interface authentication to prevent unauthenticated configuration changes via the SSO Connect admin port.

  • Removed the keycloak-services dependency (100+ transitives eliminated) to minimize CVE exposure and reduce distribution footprint.

  • Added account-switching session token passthrough for Vault Web integration.

  • Keycloak SAML dependency version updated to maintain alignment with the current release line.

Security & Bug Fixes

  • KSC-524 — SAML authentication bypass via signature relocation vulnerability mitigated by enforcing that each assertion's signature cryptographically covers the assertion it is attached to. The exploit path was validated, remediated, and regression-tested across ADFS, Okta, and Entra ID configurations.

  • KSC-518 — Administrative interface authentication bypass mitigated by correcting the session validation ordering. Previously, an unauthenticated attacker with network access to the admin port could overwrite SSO Connect configuration. The fix ensures authentication is validated before session state is updated.

    No admin-side configuration updates are required.

    We recommend validating SSO sign-in with your IdP (Okta, Entra ID, ADFS, Ping, Keycloak) in a non-production environment prior to production rollout.

Compatibility & Upgrade Notes

  • No admin-side configuration updates are required.

  • We recommend validating SSO sign-in with your IdP (Okta, Entra ID, ADFS, Ping, Keycloak) in a non-production environment prior to production rollout.

Last updated

Was this helpful?