Can an intercept trigger a re-resolution of attributes?

[Cantor, Scott]

On 8/4/16 2:56 PM, Christopher Bongaarts wrote:
> 
> I suspect using the child lookup or create helper is fine here despite
> this strategy being lookup only.

Only difference is that it will create one to return if there isn't one.

> The data connector appears to still read all the attributes - doesn't
> appear that simply defining the attributesToResolve on the resolve
> action bean is sufficient to limit it at that level, though it does dump
> all the attributes except for the attributesToResolve after looking them
> up.  It may end up faster that way anyway in our environment, since LDAP
> can leverage its entry cache if nothing's changed yet.

If you resolve an attribute, it will resolve the dependencies of just
that attribute, but if that's still your main LDAP query, then it's
going to run that query. It won't resolve all the attributes on top of
that query. You're telling it what IdPAttribute to resolve.

Keep in mind that if the LDAP connector is caching, that's going to
cause problems getting it to re-resolve the data since it will just give
you back the same results.

-- Scott