Trying to figure where the problem is:

Dave Lewney d.m.lewney at sussex.ac.uk
Mon Sep 26 09:26:13 BST 2011


On 23 Sep 2011, at 21:39, Daniel Fisher wrote:

> On Fri, Sep 23, 2011 at 4:09 PM, Leonard Kroll <Leonard.Kroll at umb.edu> wrote:
> I am new to the LDAP world.
> Ok, I am now using the full DN in the bindDN field, I get an error 32, which means no data found.
> 
> Ldapsearch reads the LDAP fine using the same DN.
> 
> CN=aaaa bbbb, OU=sssssss,dc=umassb, dc=net.
> 
>  
> 
> Any Ideas how to get around this problem.
> 
>  
> 
>  
> 
> 16:00:24.348 - TRACE [edu.vt.middleware.ldap.auth.SearchDnResolver:200] -   config = {java.naming.provider.url=ldap://xxx.xxx.xxx.xxx ldap://xxx.xxx.xxx.xxx, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, baseDN=dc=umassb,dc=net}
> 
> 
> Looks like you're setting 'baseDN', that should be 'baseDn'. Not sure if that's your only problem, but fix that and report back.
> 
> --Daniel Fisher
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

LDAP code 32 often means you've specified an incorrect basedn. Have a look in your LDAP logs. 

Dave
---
Dave Lewney
IT Services, University of Sussex, Brighton BN1 9QT



More information about the users mailing list