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-30: Authentication to extend Credentials #295

Closed
spring-projects-issues opened this issue Jul 4, 2005 · 1 comment
Closed

SEC-30: Authentication to extend Credentials #295

spring-projects-issues opened this issue Jul 4, 2005 · 1 comment
Labels
in: core An issue in spring-security-core status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement type: jira An issue that was migrated from JIRA
Milestone

Comments

@spring-projects-issues
Copy link

Ben Alex(Migrated from SEC-30) said:

As per discussion with Keith, refactor AuthenticationManager/Provider to have a public Authentication authenticate(Credentials).

Then, have Credentials hold the getPrincipal() and getCredentials() methods, with Authentication extending Credentials with the remaining methods.

@spring-projects-issues
Copy link
Author

Ben Alex said:

Whilst there are explanatory advantages in differentiating between an Authentication request and a populated Authentication object, there are no technical advantages in doing so that I can identify. I have investigated implementing this change and it would cause significant changes throughout many classes, and create backward compatibility issues for the commonly-implemented AuthenticationProvider interface. There are some issues in particular related to needing to cast (and assuming the SecurityContextHolder contains a particular type of Authentication vs AuthenticationRequest at a particular time) and also with RMI propagation of the SecurityContext. These issues are more likely to lead to bugs or configuration issues/confusion for users, and given there is no technical advantage in this change I suggest we don’t make it.

@spring-projects-issues spring-projects-issues added in: core An issue in spring-security-core Closed type: enhancement A general enhancement status: declined A suggestion or change that we don't feel we should currently apply type: jira An issue that was migrated from JIRA labels Feb 5, 2016
@spring-projects-issues spring-projects-issues added this to the 0.9.0 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 An issue in spring-security-core status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement type: jira An issue that was migrated from JIRA
Projects
None yet
Development

No branches or pull requests

2 participants
@spring-projects-issues and others