SAML Application complains about assertions are not signed
Hi,
Use-case: I try to onboard an SAML Application, after exchanging metadata, login fails
Environment: Self Hosting
Version: v2.71.15
Stack: n/a
What you expected to happen: Login to application should work
What went wrong: SP Reports Assertion is not signed:
Errorlog from Application "Invalid SAML SSO assertion: The Message of the Response is not signed and the SP requires it"
In the metadata from the SP the Descriptor is
looks like same problem as in https://github.com/zitadel/zitadel/discussions/9049
i'm using an action to add an SAML Attribute. maybe this breaks the Assertion Signing
Any hints are very welcome.
Thanks
Thomas
Use-case: I try to onboard an SAML Application, after exchanging metadata, login fails
Environment: Self Hosting
Version: v2.71.15
Stack: n/a
What you expected to happen: Login to application should work
What went wrong: SP Reports Assertion is not signed:
Errorlog from Application "Invalid SAML SSO assertion: The Message of the Response is not signed and the SP requires it"
In the metadata from the SP the Descriptor is
<md:SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true"looks like same problem as in https://github.com/zitadel/zitadel/discussions/9049
i'm using an action to add an SAML Attribute. maybe this breaks the Assertion Signing
Any hints are very welcome.
Thanks
Thomas
GitHub
I am trying to set up a Databricks workspace with Zitadel as the IDP, as described here: https://docs.databricks.com/en/archive/single-sign-on/index.html#verify-that-the-saml-response-is-signed I c...
