-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Support signing SAML metadata #14916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @CrazyParanoid! I've left some feedback inline.
...a/org/springframework/security/saml2/provider/service/metadata/OpenSamlMetadataResolver.java
Show resolved
Hide resolved
...a/org/springframework/security/saml2/provider/service/metadata/OpenSamlMetadataResolver.java
Outdated
Show resolved
Hide resolved
...a/org/springframework/security/saml2/provider/service/metadata/OpenSamlMetadataResolver.java
Outdated
Show resolved
Hide resolved
8e50e3c
to
a69f0e9
Compare
Hi @jzheaux ! Thanks for your feedback. All your comments have been resolved. |
@CrazyParanoid thanks for your contribution. Line 215 in e92dd02
If we sign EntityDescriptor before calling OpenSamlMetadataResolver.serialize, the marshaller in there will create a brand new XMLSignature object.
Where it should be
Beside that, the test case is check only whether DigestValue and SignatureValue is existing or not. I noted all debug steps at my environment (with Spring Security 6.2.2) here Please correct if I misunderstood this situation. |
Hi @longgt ! In the
I can add a value check to the test, but apparently there is no problem here. |
Thanks, @CrazyParanoid! This is now merged into |
Because I think this may become the default in the future, I made a polish of 6695784 to notify that metadata is unsigned. |
Closes gh-14801