Occasionally, SAML SSO integrations may fail after scheduled security maintenance—usually when the identity provider (IdP) rotates or updates their signing certificate, a standard best practice. When this happens, your users may see errors similar to:
⚠️ Invalid assertion. invalid signature: the signature value is incorrect
This indicates that your service (the Service Provider or SP) is no longer able to verify the signatures from your IdP, because it is using an outdated certificate. Resolving this typically requires refreshing the IdP’s connection settings.
How to Fix Certificate Rollover Errors in SAML SSO
. Identify the Problem
Confirm that users are experiencing SSO login failures and check for error messages about “invalid signatures” or “invalid assertion.”
Reach out to your IdP administrator or review any recent notification of certificate changes or upcoming maintenance.
Refresh or Update SAML Metadata
Most modern SAML IdPs provide a “metadata URL”—an XML document containing the current signing certificates and endpoints.
Locate the Metadata URL: Obtain the metadata URL from your identity provider (e.g., your ADFS admin, Microsoft Azure AD, Google Workspace, Okta, or Auth0 dashboard).
Refresh Metadata in Sleekplan:please contact Support in order to obtain a setup link to update the metada from you IdP :
