Mailing-List: contact jsecurity-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jsecurity-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <8bd9fdba0810070551y36e6578di2165c2c16b04c521@mail.gmail.com>
Date: Tue, 7 Oct 2008 13:51:40 +0100
From: "Peter Ledbrook" <peter@g2one.com>
To: user@grails.codehaus.org
Subject: Re: [grails-user] JSecurity Plugin, AbstractLdapRealm and Caching
Cc: "JSecurity Developer List" <jsecurity-dev@incubator.apache.org>
In-Reply-To: <19843999.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <19843999.post@talk.nabble.com>

Hi,

I'm forwarding this to the JSecurity mailing list since it relates the
the core JSecurity classes.

Cheers,

Peter

2008/10/6 Skowronek <tskowronek@wi.rr.com>:
>
> I have a Grails application using version 1.0.3.  The JSecurity plugin
> version 0.3-SNAPSHOT is installed.
>
> I created a realm called AdamRealm, which extends AbstractLdapRealm to take
> advantage of the services in the hierarchy.  Specifically caching.
> AdamRealm is very similar to ActiveDirectoryRealm.
>
> After launching the app, the realm is created as well as the CacheManager as
> shown in the log entries below.
>
> [com.jud.realm.AdamRealm] AdamRealm created
> [org.jsecurity.mgt.CachingSecurityManager] Attempting to initialize default
> CacheManager using EhCache...
> [org.jsecurity.cache.ehcache.EhCacheManager] cacheManager property not set.
> Constructing CacheManager instance...
> [org.jsecurity.io.ResourceUtils] Opening resource from class path
> [org/jsecurity/cache/ehcache/ehcache.xml]...
> [org.jsecurity.cache.ehcache.EhCacheManager] instantiated Ehcache
> CacheManager instance.
> [org.jsecurity.cache.ehcache.EhCacheManager] implicit cacheManager created
> successfully.
>
>
> If a user tries to access a restricted resource for the first time, I see
> that the queryForAuthenticationInfo(AuthenticationToken token,
> LdapContextFactory ldapContextFactory) implementation is called as expected
> and the user is authenticated.
>
> [com.jud.realm.AdamRealm] queryForAuthenticationInfo started
> DEBUG [org.jsecurity.authc.AbstractAuthenticator] Authentication successful
> for token [org.jsecurity.authc.UsernamePasswordToken - abc00,
> rememberMe=false].  Returned account:
> [org.jsecurity.subject.SimplePrincipalCollection@3fe59b3e]
>
>
> Next, the the queryForAuthorizationInfo(PrincipalCollection principals,
> LdapContextFactory ldapContextFactory) implementation is called as expected
> since this is the first time a restricted resource is being accessed by the
> user.
>
> DEBUG [com.jud.realm.AdamRealm] queryForAuthorizationInfo started
>
> My understanding is that for all subsequent requests made by the user, the
> queryForAuthorizationInfo() shouldn't be called.  Instead,
> AuthorizingRealm.getAuthorizationInfo(PrincipalCollection principals) should
> pull the AuthorizationInfo from the cache, but that doesn't happen.  For
> every subsequent request, I see the queryForAuthorizationInfo() being
> called.
>
> Any assistance on how to get the realm to pull the AuthorizationInfo from
> the cache would be appreciated.
>
> Thank you.
>
> --
> View this message in context: http://www.nabble.com/JSecurity-Plugin%2C-AbstractLdapRealm-and-Caching-tp19843999p19843999.html
> Sent from the grails - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>


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