Resolver plugin 'myLDAP' produced no value

[Naveed Hashmi]

Thanks Rob/Peter.

I can see the following in the process log when 'upping' the log levels ..

DEBUG
[net.shibboleth.idp.attribute.resolver.spring.dc.ldap.impl.LDAPDataConnectorParser:119]
- Data Connector 'myLDAP': Parsing v2 configuration
[resolver:DataConnector: null]

DEBUG
[net.shibboleth.idp.attribute.resolver.dc.ldap.impl.TemplatedExecutableSearchFilterBuilder:212]
- Template text uid=$({requestContext.principalName}) yields
uid=$({requestContext.principalName})

DEBUG
[net.shibboleth.idp.attribute.resolver.dc.ldap.impl.StringAttributeValueMappingStrategy:60]
- Results did not contain any entries, nothing to map

I'm using the same ldap (data connector) config values as per idpV2 ...
 hence the principal that binds to my directory has appropriate rights to
read the source attributes. However the above indicate a problem with
parsing? i.e. returns a 'null' for the data connector or a problem with the
search filter?

Naveed

On 22 February 2016 at 11:25, Rod Widdowson <rdw at steadingsoftware.com>
wrote:

>  > Any help appreciated.
>
> In addition to Peter's excellent (as always) advice I'd suggest that you
> turn up logging to debug for net.shibboleth.idp.attribute.resolver and
> possible for ldaptive.
>
> Either do it in logback.xml or via the properties  idp.loglevel.idp and
> idp.loglevel.ldap
>
> /Rod
>
>
> --
> 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/20160222/ee4ecd88/attachment.html>