Activation Condition Predicate for an Empty Attribute
cantor.2 at osu.edu
Thu Aug 10 15:57:27 EDT 2017
> Right, I know that, that's not what I intended to convey. What I intended to
> convey was just that because:
> > [...] it would copy the empty/null slots out into the visible IdPAttribute.
> then for any DataConnector that returns null valued source attributes,
> wildcard searching on any attribute that is even in the schema (object or
> table, RDBMS or LDAP) of the connected source always returns true.
If you construct your final results that way. I always filter out the empties in various ways on top, so I never noticed it was doing that. My backfill logic is already done by the time the resolver completes, so "mail" always has "the right answer" regardless of where it happened to come from. In my case, I have to do that with employee ID, which is null for guests and such, and I have to backfill.
Having said that, it does what it does, and behavior like that is locked in once it's been shipped, so it's mostly academic at this point, with an enhancement now to actually work around the behavior optionally.
More information about the users