-
Notifications
You must be signed in to change notification settings - Fork 6k
Saml2WebSsoAuthenticationFilter ignores the authentication details #7722
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
Comments
I feel these two issues are related, and one solution could satisfy both |
…thentication details with AbstractAuthenticationProcessingFilter 'authenticationDetailsSource'
I'm not really sure if this issue relates to the UserService and AuthenticatedPrincipal... Please see this commit for more information on what I'm trying to achieve (same mechanism as UsernamePasswordAuthenticationFilter). |
Copying the details within the authentication provider is not needed as they are copied inside the |
@horca, thanks for laying out some of the details here. I think it makes sense to have the SAML 2.0 support align with other authentication filters in Spring Security. Would you be interested in submitting a PR to have the filter set the details object on the |
@jzheaux I would love to give it a try if its open for contribution. Can you please explain litte more on what is the implementation plan? |
Hello Spring Security team,
Problem
When using the
UsernamePasswordAuthenticationFilter
we are setting custom authentication details withAuthenticationDetailsSource
to be used further down the security chain. Unfortunately, theSaml2WebSsoAuthenticationFilter
does not populate the authentication details even though it inherits fromAbstractAuthenticationProcessingFilter
which allows to define the details source.Solution
After the
Saml2AuthenticationToken
is created, populate the details. Afterwards, when creating theSaml2Authentication
within the authetication provider, just copy the details over.The text was updated successfully, but these errors were encountered: