Attribute resolver dependency question/issue

[Tom Poage]

On 05/07/2012 11:01 AM, Cantor, Scott wrote:
> On 5/7/12 1:47 PM, "Tom Poage" <tfpoage at ucdavis.edu> wrote:
> 
>> Debug trace. Why would eduPersonAffiliation not be cached?
> 
> The only caching is the data connectors. The result set of the resolver on
> the whole is not cached.
> 
>> Does the attribute filter operate on the cached LDAP data, so if I
>> filter it out in attribute-filter.xml, it's gone 'forever'?
> 
> No. It's manipulating the released attributes, not acting on the data
> connector results. Since the attribute defs are not cached in any sense,
> the filter can't influence anything that's cached.

OK, that's what I thought.

Still can't explain why on first authN a single ePA value is pulled from
the LDAP directory, and on second authN *zero* ePA values are in the
LDAP cache, even though all other attributes seem to be cached properly.

I would think the Script AttributeDefinition of ePA that relies on the
directory ePA value wouldn't affect what's maintained in the LDAP cache.
Hmm, maybe I should just turn off the LDAP cache altogether.

> <resolver:AttributeDefinition id="eduPersonAffiliation" xsi:type="ad:Script" sourceAttributeID="eduPersonAffiliation">
>    <resolver:Dependency ref="ucdLDAP" />
...

Tom.