Hey folks,
Earlier today I wrote up a JIRA for an issue I discovered working for
Ohio University:
- http://www.ja-sig.org/issues/browse/UP-2698
Here it is, in a nutshell...
Although CacheSecurityContext states (in it's Javadoc) that it can be
used or "chained" with any security context capable of authenticating
users, it doesn't actually work with any of them *except*
SimpleSecurityContext.
This bug is due to the fact that it consults the AccountStore, which
performs a lookup on the UP_PERSON_DIR table.
I proposed fixing this bug by taking out the lookup, and instead
verifying that the "parent" (chained) security context was able to
authenticate the user before caching the credentials.
I also attached a patch to the JIRA.
Once this patch is applied, CacheSecurityContext should -- when properly
configured -- be able to work with any security context that implements
ChainingSecurityContext.
Cheers,
drew wills
--
Andrew Wills
UNICON, Inc.
Office: (480) 558-2476
http://cernunnos.googlecode.com/
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
