Getting error "Invalid Attribute resolver configuration"

[Jeremy Morton]

On 29/01/2015 21:09, Cantor, Scott wrote:
>> I need to know how to match it up with my AD users, whose objects are in
>> the form "CN=User Name".  And again, is there some way I can see log
>> output of how Shibboleth is trying to match stuff up?  All I know so far
>> is that it doesn't seem to be bringing back any attributes, but I don't
>> know why.
>
> On DEBUG you should get plenty of that information.

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.  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!!

eg.
sourceAttributeID="sAMAccountName" doesn't work
sourceAttributeID="samaccountname" works

-- 
Best regards,
Jeremy Morton (Jez)