-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Resource Server Package Name Inconsistencies #7349
Comments
|
@jgrandja, I see that
By these it seems to me that authentication filters go into What am I missing regarding the packaging conventions? |
@jzheaux Thanks for providing references to existing authn |
I'd have to give this some thought. At first glance I'd say that they should be in web.authentication. I'm trying to remember if there were any conscious decisions to make the packages less sparse by avoiding an authentication package. It could be argued that cas in itself implies authentication, so perhaps that is reason enough to avoid another authentication package. |
Some of the classes in
oauth2-resource-server
could be better aligned with the whole.For example, if
XYZ
represents the root package for that module, then:XYZ.web.authentication
, butBearerTokenAuthenticationFilter
is only inXYZ.web
XYZ.authentication
, butBearerTokenAuthenticationToken
is inXYZ
Since these have both GA'd already, they likely won't be adjusted on the 5.x release train, but I'm recording this for future reference.
The text was updated successfully, but these errors were encountered: