Attribute resolver and failed data connector

[Michael A Grady]

This is with IdP 3.3.1, and  bean-managed DB connectors. There are three DCs, one to DB, 2nd to DB that relies on querying based on attribute returned by the 1st DB connector, and a 3rd that goes to LDAP. There are a few users just in LDAP, not in DB. The LDAP connector succeeds, and pulls in some attributes. That first DB connector returns no entry, which the resolver doesn't flag as an error (unless I was to set noEntry is error.) But that 2nd DB connector does "error out" -- presumably since the first connector didn't fail, the 2nd connector's dependency on the attribute returned by the 1st was considered satisfied, but that attribute didn't get a value. That error causes the resolver to end up without an "Attribute Context", even though the LDAP connector succeeded and pulled in attributes.

Expected or a "bug"? Solved it with a static failover connector for the DB connector, but was curious if that is expected behavior, or is there a different way I should have configured the dependency of the 2nd DB connector that wouldn't have tried to "fire it"?

--
Michael A. Grady
IAM Architect, Unicon, Inc.