-
Notifications
You must be signed in to change notification settings - Fork 1.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
The UserStore and PropertyUserStore classes are hard to re-use for caching eg JDBC data #5272
Labels
Comments
janbartel
added a commit
that referenced
this issue
Nov 11, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel
added a commit
that referenced
this issue
Nov 12, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel
added a commit
that referenced
this issue
Nov 12, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel
added a commit
that referenced
this issue
Nov 17, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel
added a commit
that referenced
this issue
Nov 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
9.4.x
The o.e.j.security.UserStore and o.e.j.security.PopertyUserStore classes are hard to re-use. The intention is to provide an L1 cache of user authentication and authorization information, with the various XXXLoginService classes providing the interface to the persistent store. However, the way the classes are currently written, they are only used by the HashLoginService class. Some of the behaviour of the PropertyUserStore could usefully be incorporated into the UserStore to provide a cache that can periodically be emptied/replenished from the XXXLoginService classes.
The text was updated successfully, but these errors were encountered: