Certificate not matching in SAML response and federation metadata causing signature not valid

Hi,

Certificate not matching what provided in SAML response and federation metadata causing SAML assertion signature not valid. We have validated the ID provided while request and in response and it matched.

Please help us how to address this issue.

Regards,
Alagumuthu

Alagumuthu Melur dhandapani 6 Reputation points

2022-03-18T06:12:06.397+00:00

What might be reason the signature is different ? Please help on this issue.
Givary-MSFT 30,931 Reputation points Microsoft Employee

2022-03-21T06:48:38.927+00:00

@Alagumuthu Melur dhandapani

Apologies for the delay in reaching out to you. Are you still facing this issue ?

Have you used the right certificate ( format ) and uploaded the same ?

Can you share the screenshots of the issue ?
Alagumuthu Melur dhandapani 6 Reputation points

2022-03-21T07:46:33.697+00:00

Hi Girish,

yes, still issue persists. We are actually passing to value to the program for validation. One is the Federation Metadata XML(refer the below) and the Base64 encoded response. Our response is Assertion signed. X.509 certificate present in Federation metadata xml and in response which used for sign the asserstion should match, but is different. Hence we are getting error "signature not valid, signature cryptographic validation not successful".

Both the certificate should match in order to validate the source. Please help us in which scenario, Azure is sending the different certificate which is not in federation metadata.
Eder Anillo 6 Reputation points

2022-06-10T13:49:00.627+00:00

Hi guys

Any update?
Eder Anillo 6 Reputation points

2022-06-10T14:01:52.327+00:00

Hello guys
Anything else?

Share via

Certificate not matching in SAML response and federation metadata causing signature not valid