Mailing-List: contact jsecurity-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jsecurity-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of tskowronek@wi.rr.com
 designates 71.74.56.125 as permitted sender)
From: "Thomas Skowronek" <tskowronek@wi.rr.com>
To: <user@grails.codehaus.org>
Cc: <jsecurity-dev@incubator.apache.org>
Subject: RE: [grails-user] JSecurity Plugin, AbstractLdapRealm and Caching
Date: Fri, 17 Oct 2008 09:59:17 -0500
Message-ID: <56C068CD9A2D478C9BFC6C102FD0F68F@JAVAONE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckwGpEx+Co1Udf0TyW/5nZJ/HG/VgAThOJg
In-Reply-To: <8bd9fdba0810162237k496d73a5h31254ce8c48ccb72@mail.gmail.com>

Les and Peter,

Making the following change fixed the problem.  Subsequent requests are now
accessing the cache.

"mgr.realms += beans.collect { applicationContext.getBean(it) }"

Thanks for all your help on this issue.  I really appreciate it.

Best regards,

Thomas

-----Original Message-----
From: Peter Ledbrook [mailto:peter@g2one.com] 
Sent: Friday, October 17, 2008 12:38 AM
To: user@grails.codehaus.org
Cc: jsecurity-dev@incubator.apache.org
Subject: Re: [grails-user] JSecurity Plugin, AbstractLdapRealm and Caching

> DefaultWebSecurityManager securityManager = new
DefaultWebSecurityManager();
> securityManager.init(); // <-- the securityManager has a default
> EhCacheCacheManager if ehcache is in the classpath, but your Realm
> doesn't have it yet
>
> securityManager.setRealm( myRealm );
> //now 'myRealm' will have the cacheManager instance and its
> AuthorizationInfo cache will be created.

Ah, I think I can see what the problem is. The normal realms
configured by the plugin are added in the bean definition, so they
will be initialised during "securityManager.init()". However, I add
native JSecurity realms once the security manager has been
instantiated:

100 	        // Finally add the remaining beans to the security manager.
101 	        log.info "Registering native realms: $beans"
102 	        def mgr = applicationContext.getBean('jsecSecurityManager')
103 	        mgr.realms.addAll(beans.collect {
applicationContext.getBean(it) })

Since I'm adding the beans to the existing realms collection, the
cache manager stuff is not triggered for those realms. This is already
a hack, since plugins can't see bean definitions from
"resources.groovy" or "resources.xml". I could just call "mgr.realms
+= beans.collect { applicationContext.getBean(it) }".

Cheers,

Peter

-- 
Software Engineer
G2One, Inc.
http://www.g2one.com/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email