-
Notifications
You must be signed in to change notification settings - Fork 4
SAML2 logout feedback #29
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
base: saml2-logout
Are you sure you want to change the base?
Conversation
| return new Saml2AssertingPartyInitiatedLogoutSuccessHandler(responseResolver()); | ||
| } | ||
|
|
||
| @Bean |
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.
It seems like requestResolver() and requestResolver() don't need to be beans
| return http.build(); | ||
| } | ||
|
|
||
| @Bean |
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.
It seems like the logoutSuccessHandler doesn't need to be a bean either.
| public OpenSamlLogoutRequestSpec resolveLogoutRequest(HttpServletRequest request, | ||
| RelyingPartyRegistration registration, Authentication authentication) { | ||
| return new OpenSamlLogoutRequestSpec(registration) | ||
| .destination(registration.getAssertingPartyDetails().getSingleLogoutServiceLocation()) |
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.
Why do only destination, issuer and name have default values?
| .name(authentication.getName()); | ||
| } | ||
|
|
||
| public class OpenSamlLogoutRequestSpec implements Saml2LogoutRequestSpec<OpenSamlLogoutRequestSpec> { |
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.
Does it make sense to allow users to conveniently change the destination, issuer and name?
Is there a use case where they would want those values to be different than what they set up in the RelyingPartyRegistration?
a88c1b1 to
ddf8e7a
Compare
2ee9b25 to
f16548f
Compare
ebf88c5 to
2c6c988
Compare
d547bad to
86f6b95
Compare
4d82f8c to
6038bdb
Compare
25d7d4b to
a96844b
Compare
30bb291 to
4b29450
Compare
No description provided.