Azure AD B2C Saml Assertions Not Signed

Question

Hello,

We are trying to integrate into an application that only supports SAML IDP-initiated authentication. SP is not supported.

However, when we try to authenticate, we are getting an error saying that the assertion is not signed.

We have tried setting the metadata value: WantsSignedAssertions to true, but when we view the SAML response, it does not show a signature element within the Assertion Element.

Any help would be greatly appreciated.

Answer 1

@Christopher Norris ,

Kindly validate the value for ResponsesSigned attribute. If the value is set to false, the identity provider shouldn’t sign the SAML response, but even if it does, Azure AD B2C won’t validate the signature. If you disable the SAML response validation, you also may want to disable the assertion signature validation

Please do let me know if you have any queries in the comments section.

Thanks

Akshay Kaushik

Please "Accept the answer" (Yes/No), and share your feedback if the suggestion works as per your business need. This will help us and others in the community as well.

Answer 2

@Christopher Norris ,

Thanks for your response. This attribute is not required but has to be added in metadata. For example:

Possible values are true/false as per Define a SAML identity provider technical profile :

For a deep-dive kindly refer to Azure AD B2C Custom Policies - Deep Dive

Thanks,

Akshay Kaushik

Please "Accept the answer" (Yes/No), and share your feedback if the suggestion works as per your business need. This will help us and others in the community as well.