Skip to content
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

SEC-618: Authentication details object should be copied to successful Authentication before ConcurrentSessionController.checkAuthenticationAllowed is called #879

Closed
spring-projects-issues opened this issue Dec 6, 2007 · 1 comment
Labels
in: core type: bug type: jira
Milestone

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Dec 6, 2007

Luke Taylor(Migrated from SEC-618) said:

If concurrent session control is used with an authentication provider which doesn’t copy the authentication details object to the successful authentication (e.g. CasAuthenticationProvider) then the check with the concurrent session controller on whether access is allowed takes place before the copyDetails method of AbstractAuthenticationManager is called. This isn’t a problem with classes which extend AbstractUserDetailsAuthenticationProvider, as it copies the authentication details object itself.

The copyDetails method should probably be pulled down into ProviderManager and called before checkAuthenticationAllowed() is called. This will ensure that the details object is available even if the provider doesn’t set it.

It’s also not clear that we really need an AbstractAuthenticationManager at all, given how little there is in there.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Dec 7, 2007

Luke Taylor said:

I’ve made the suggested change on both trunk and 1.0.x branches.

@spring-projects-issues spring-projects-issues added in: core Closed type: bug type: jira labels Feb 5, 2016
@spring-projects-issues spring-projects-issues added this to the 2.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core type: bug type: jira
Projects
None yet
Development

No branches or pull requests

1 participant