Then we may need to think about more loosely coupling authorization information from the authenticated Subject through some indirection mechanism. A PasswordCredential is really an attribute of the authenticated Subject that may not have any relation to the credentials used to authenticate the Subject. Multiply this across all of the resources the Subject interaces with and you get the restart of a single resource adaptor flushing the entire state of the Subject and this is too coarse grained.
> > Caching is not part of any of the manifest security manager related > > interfaces > > so there is not a single reference you can obtain short of going to the > > org.jboss.security.plugins.JaasSecurityManager object which is not a good > > idea. > > In what circumstances do you flush the cache? This should really not be a > > framework level event. > > The jca PasswordCredential includes an object reference to the > ManagedConnectionFactory it is for. When a ConnectionManager is stopped > and restarted, you get a different ManagedConnectionFactory instance. The > only way I have found to make sure that subsequent logins get the new > reference is to flush the cache. I'm using mbean notifications from the > ConnectionManager mbean to the login module to tell the login module its > ManagedConnectionFactory reference is outdated, but that doesn't do > anything to the cached Subject. > > thanks > david jencks _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
