Resolver plugin 'myLDAP' produced no value
Naveed Hashmi
Naveed.Hashmi at bristol.ac.uk
Mon Feb 22 05:49:52 EST 2016
Hi,
I'm having problems configuring a test IdP v3 to use LDAP for attribute
resolution (we use CAS for auth which is working). My attribute resolver
looks something like the following ..
<resolver:DataConnector id="myLDAP" xsi:type="dc:LDAPDirectory"
ldapURL="ldaps://ldap-org.edu:636"
baseDN="cn=Users,dc=xxxx,dc=xx,xx=xx"
principal="uid=xxxx,ou=xxxx,dc=xx,dc=xx,dc=xx"
principalCredential="..."
useStartTLS="false">
<dc:FilterTemplate>
<![CDATA[
uid=$({requestContext.principalName})
]]>
</dc:FilterTemplate>
</resolver:DataConnector>
The attribute definitions have been configured so the following are sourced
via 'myLDAP' : 'eduPersonPrincipalName', 'uid' and 'mail'.
I have updated the attribute filter to release these attributes to TestShib.
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.
I suspect I need to set 'useSSL' to 'true' but this can only be done if you
use ldap for authentication?
Any help appreciated.
Naveed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160222/6b4cb2db/attachment.html>
More information about the users
mailing list