Provider changes/ClerkCLERK · VERIFIED CHANGE

Clerk SAML connections now support up to five signing certificates for overlapping key rotation

Clerk SAML connections now support up to five signing certificates for overlapping key rotation. Certificate management adds full-list API updates and PEM bundle uploads; the legacy idp_certificate field remains functional but is deprecated.

Verified Oct 26, 20264 official sources

Mentioned in the evidence

  • Clerk SAML enterprise connections
  • Backend API idp_certificates
  • Backend API idp_certificate
  • Clerk Dashboard
  • <OrganizationProfile />

Official sources

  • Clerk product changelog (changelog) ↗
    Multiple certificates are available on every instance with SAML enterprise connections; existing connections keep their current certificate as the only entry until you add more.
  • Clerk product changelog (changelog) ↗
    A SAML enterprise connection now trusts up to five signing certificates at once.
  • Clerk product changelog (changelog) ↗
    Backend API: pass the full list as idp_certificates when you create⁠ or update⁠ an enterprise connection; responses include each certificate with its validity window. The single idp_certificate field keeps working, accepts a PEM bundle, and is deprecated.
  • Clerk product changelog (changelog) ↗
    Changing a connection's certificates replaces the entire list with the certificates you provide. If an update doesn't include certificates, the list stays the same.

This is a global change, verified against Clerk’s own sources. It is not an assessment of your systems or your impact.

A global change is not your impact.

Auterim checks your confirmed dependencies and can verify repository references when GitHub is connected.