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

Jump to bottom

Backup Shiro init uses new instances of SecurityManager and Realm(s) #56

Closed
GoogleCodeExporter opened this issue May 3, 2015 · 1 comment
Closed

Backup Shiro init uses new instances of SecurityManager and Realm(s) #56

GoogleCodeExporter opened this issue May 3, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

This erroneously creates multiple versions of security managers, caches, etc.
The backup shire init logic should use only one instance of everything.

Original issue reported on code.google.com by lennypri...@gmail.com on 30 Dec 2013 at 1:50
@GoogleCodeExporter
Copy link
Author 

This issue was closed by revision 5f08bfbe2d8d.

Original comment by lennypri...@gmail.com on 30 Dec 2013 at 2:00

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter