Resolver plugin 'myLDAP' produced no value

[Peter Schober]

* Naveed Hashmi <Naveed.Hashmi at bristol.ac.uk> [2016-02-22 11:50]:
> The ldap.properties files has been left as per default. I have set the
> logging to debug for 'idp.loglevel.ldap. The idp starts up OK, but is
> unable to get hold of the attributes post authentication ... the idp
> process log shows ..
> 
> INFO [net.shibboleth.idp.attribute.resolver.AbstractResolverPlugin:191] -
> Resolver plugin 'myLDAP' produced no value.

Make sure the principal that binds to your directory has appropriate
rights to read the source attributes for the required set of subjects.

I'd also check the logs on the LDAP server to see what the query is
(which will also confirm or rule out any TLS/SSL issues) and compare
this with what you expect it to be. (or a working example using the
ldapsearch command line tool, for example).

> I suspect I need to set 'useSSL' to 'true' but this can only be done if you
> use ldap for authentication?

The resolver has nothing to do with authentication, even if you used
the Shibboleth IDP for authentication, which you don't (I understood
you to say you're using an external CAS system).
The documentation has the relevant defaults for the TLS and SSL
settings for the LDAP DataCOnnector, if you're unsure whether that's
the cause of your issue.
-peter