Getting error "Invalid Attribute resolver configuration"

[Jeremy Morton]

OK, I figured out that it was putting some invalid credentials errors in
idp-warn.log and I was only looking at idp-process.log (I'm running this on
Windows).  I've fixed the credentials (I think) and I'm now not getting
that error; however, I am still not getting my "mail" attribute returned to
the SP upon login.  It simply returns my test static attribute.  So there
seems to be a problem with the baseDN and FilterTemplate setup, such that
it's not finding anything.

Is there any in-depth documentation on how FilterTemplate works here?
Like, I've seen in examples that you can use $requestContext.principalName
in there, but how does $requestContext.principalName get set?  What does it
get set to?  Would it be "Joe.Bloggs" or "Joe Bloggs" or "Joe.Bloggs at domain"
or what?  And what else can I use in there?  I really need an in-depth look
at how Shibboleth is attempting to match the LDAP data to figure out what's
going wrong.

Best regards,
Jeremy Morton (Jez)

On Thu, Jan 29, 2015 at 4:19 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > However, I can't see any error with my DataConnector.  When I comment out
> > its XML, though, the error doesn't happen, so I guess that is where the
> error
> > lies.  Here is my XML file:
> > http://pastebin.com/CbKCzgAM
>
> If there's an error with it, the log should indicate that during startup.
>
> > By the way, just a suggestion, but you guys could do with a more
> meaningful
> > error message here.  I have no idea why component is apparently null, and
> > only that one ERROR in my logfile.  Any ideas why it isn't working?
>
> No, there should be more than just that one ERROR in the log unless
> something's very wrong.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150129/23578d66/attachment.html