Hi,

The Shiro plugin for Grails tries to support automatic reloading of
realms. So when a user modifies a realm while the application is
running, the change takes effect almost immediately without the user
having to restart the servlet container. A side-effect of this feature
is that the security manager bean is reloaded. In other words, you get
a new instance of the security manager.

The problem I'm facing is that the subject never gets updated with the
new security manager, so the user's changes to his or her realm don't
take effect as they should. I was using a nasty hack via Groovy to
update the securityManager field on the subject directly, but it is a
hack. Are there any other ways of updating the subject? Maybe creating
a new delegating subject with the new security manager? If not, any
ideas for changes to Shiro that might aid this?

Thanks,

Peter

Reply via email to