Getting error "Invalid Attribute resolver configuration"

[Jeremy Morton]

On 29/01/2015 19:14, Cantor, Scott wrote:
>> Is there any in-depth documentation on how FilterTemplate works here?
>
> Not yet, though all the javadocs are in place if you're getting into really hairy stuff, which you're not.
>
> FWIW, the file you posted had no LDAP connector in it at all, other than the commented out example.

Yes it did, starting on line 200. :-)

>> Like, I've seen in examples that you can use $requestContext.principalName
>> in there, but how does $requestContext.principalName get set?
>
> The canonicalized principal name resulting from authentication is what's in it.

So what, in practice, is that?  If the user logs in as 
"Joe.Bloggs at domain.com", what will it be?  If the user logs in as "Joe 
Bloggs", what will it be?  If the user logs in as "xyz\Joe Bloggs", what 
will it be?

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.

>> And what else can I use in there?
>
> Lots of other data reachable from the requestContext object, but it virtually never matters.

Again, not documented?

-- 
Best regards,
Jeremy Morton (Jez)