Answered by:
Invalid Signature on SAML Response

Question
-
Hi,
ADFS SSO was working.. and then it wasn't.
All sites except Office365 are giving me Invalid Signature or bad signature response.
What I've tried so fasr:
ADPR server reinstall, ADFS basically reinstall, killed DB and recreated ADFS part. Set up everything again and yet still getting same error.
All logging, etc is is turned on, can't really find anything useful.
One maybe interesting warning which I get: Event ID 278 Source AD FS
The SAML artifact resolution endpoint is not configured or it is disabled.
The artifact resolution service is not started.
User Action
If the artifact resolution service is required, use the AD FS Management snap-in to configure or enable the SAML artifact resolution endpoint.--- Though everything seems to be switched on, etc. Valid cert, server time is fine and all that.
- Edited by Jakko Valgi Saturday, January 5, 2019 5:19 PM
Saturday, January 5, 2019 3:38 PM
Answers
-
Hi,
I think I just fixed it.
Token-signing certificate and Token-decrypting certificates .. these were the ones which I replaced.
Recreated Relaying Party Trusts and done, works.
Still wondering though, how did it work the whole time with these certs that I had there.
- Marked as answer by Jakko Valgi Monday, January 7, 2019 8:08 PM
Monday, January 7, 2019 8:27 AM
All replies
-
Hello,
Could you verify your signing certificate on ADFS Management ? It seems the RPS don't use th good one.
Blog : itpro-tips.com
itpro_tipscom
Sunday, January 6, 2019 6:28 PM -
Hi,
The certificate on ADFS side is good and valid. Got same cert on ADPR as well.
It was working just fine and then randomly one day stopped working.
Monday, January 7, 2019 7:54 AM -
Hi,
I think I just fixed it.
Token-signing certificate and Token-decrypting certificates .. these were the ones which I replaced.
Recreated Relaying Party Trusts and done, works.
Still wondering though, how did it work the whole time with these certs that I had there.
- Marked as answer by Jakko Valgi Monday, January 7, 2019 8:08 PM
Monday, January 7, 2019 8:27 AM -
Good news, the problem was related to auto renewal token certficate as I thought. Be careful next year :)
For better understanding, please refer to :
https://blogs.msdn.microsoft.com/vilath/2015/09/02/how-to-update-certificates-for-ad-fs-3-0/
Blog : itpro-tips.com
itpro_tipscom
- Proposed as answer by ITPro-Tips Monday, January 7, 2019 6:59 PM
Monday, January 7, 2019 6:59 PM