Getting error "Invalid Attribute resolver configuration"

[Cantor, Scott]

> This.  Setting a bunch of stuff in logback.xml, particularly
> org.ldaptive, to DEBUG turned out to be the best way to figure out what
> was going on with the lookup.

Certainly the LDAP material is there, yes. If we didn't include a commented out laptive category, we probably need to.

>  One odd thing that seems to happen is
> Active Directory attribute names get lowercased, *and then
> AttributeDefinition's sourceAttributeID is matched with
> case-sensitivity* to that lowercased name, so all sourceAttributeID's
> have to be lowercase even if AD Explorer shows the attribute as mixed-
> case!!

Well, the names are case sensitive once they're in the resolver, but I have no idea about the case folding. Certainly doesn't happen to me in V2 and the tests I've done with an upgraded V3 on top of that configuration.
 
-- Scott