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

[security] [config] [dynamic-config] Clarify DynamicSecurityConfig & SecurityService lifecycle #10834

vbekiaris opened this issue Jun 26, 2017 · 2 comments


Copy link

@vbekiaris vbekiaris commented Jun 26, 2017

Currently a new instance is created each time DynamicConfigurationAwareConfig.getSecurityConfig is invoked

Copy link

@mmedenjak mmedenjak commented Jul 10, 2017

@vbekiaris do you mean this lifecycle is just unclear or there is a possible bug (e.g. leak)?

Copy link
Contributor Author

@vbekiaris vbekiaris commented Jul 11, 2017

It's a leftover from #10832 , there might be a bug in DynamicSecurityConfig wrapping so created this issue to investigate further.

@mmedenjak mmedenjak changed the title Clarify DynamicSecurityConfig & SecurityService lifecycle [security] [config] [dynamic-config] Clarify DynamicSecurityConfig & SecurityService lifecycle Jul 11, 2017
@mdogan mdogan closed this in #11011 Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants
You can’t perform that action at this time.