-
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
PropertyFileLoginModule retains PropertyUserStores #5486
Comments
janbartel
added a commit
that referenced
this issue
Oct 27, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
In investigating this, I've realized the problem is worse than initially thought: the PropertyFileLoginModule keeps PropertyUserStores in a static map and never stops or removes them. I'm changing the title of the issue to reflect this. |
janbartel
changed the title
PropertyFileLoginModule does not obey the refreshInterval
PropertyFileLoginModule retains PropertyUserStores
Oct 27, 2020
janbartel
added a commit
that referenced
this issue
Nov 2, 2020
Signed-off-by: Jan Bartel <janb@webtide.com>
janbartel
added a commit
that referenced
this issue
Nov 11, 2020
Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
*9.4 and above
In older versions of Jetty, we set a "refreshInterval" property on the PropertyFileLoginModule to force it to do regular hot reloads of the configured property file cached via the PropertyUserStore class. When the PropertyUserStore changed to using PathWatcher, and the setter became hotReload=true/false rather than an interval, the PropertyFileLoginModule was not modified.
The text was updated successfully, but these errors were encountered: