You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2022. It is now read-only.
It looks like when a SP metadata has multiple certificates, spid-testenv2 rejects all AuthnRequests even if they are signed with one of those certificates. Removing the extra ones and leaving only the actually used one appears to fix the issue.
In the test case, the correct certificate was the second one listed in the metadata. So maybe spid-testenv2 is only considering the first one.
The text was updated successfully, but these errors were encountered:
Hi, I can confirm the issue: we experimented the same problem with a SP metadata that contains multiple signing certificates. As suggested, removing one of them resolved the problem.
Any estimate about the resolution?
This report should be verified.
It looks like when a SP metadata has multiple certificates, spid-testenv2 rejects all AuthnRequests even if they are signed with one of those certificates. Removing the extra ones and leaving only the actually used one appears to fix the issue.
In the test case, the correct certificate was the second one listed in the metadata. So maybe spid-testenv2 is only considering the first one.
The text was updated successfully, but these errors were encountered: