View Issue Details

IDProjectCategoryView StatusLast Update
0000670SOGoBackend Generalpublic2010-07-06 11:16
Reportertavitar Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.2.2 
Summary0000670: ldap scope 'SUB' not working
Description

When specifying the exact basedn where the user resides, authentication works fine. But using a basedn higher up the tree fails (tracing the connection shows it's attempting to bind at the basedn, instead of searching, then binding as it should).

Our ldap server is a Novell eDirectory.

Sogo settings are as follows:
sogod SOGoUserSources '(
{
CNFieldName = fullName;
IDFieldName = cn;
UIDFieldName = cn;
baseDN = "o=cathed";
bindDN = "cn=proxy-sogo,ou=proxy-user,o=cathed";
bindPassword = *****;
canAuthenticate = YES;
displayName = "Staff";
filter = "(objectClass=inetOrgPerson)";
hostname = 128.1.10.122;
id = directory;
isAddressBook = YES;
port = 389;
scope = SUB;
type = ldap;
}
)'

The LDAP server displays the following:
13:49:37 B7338BA0 LDAP: Bind name:cn=testuser,o=cathed, version:3, authentication:simple
13:49:37 B7338BA0 LDAP: Failed to resolve full context on connection 0xcf4d280, err = no such entry (-601)

The actual user is cn=testuser,ou=users,o=cathed

Please let me know if any further details are require.

Cheers,
David

TagsNo tags attached.

Activities

greenshift

greenshift

2010-07-05 08:42

reporter   ~0001147

You seem to be missing the bindFields = (uid) or whatever your login name field is. Indirect binds won't work without it.

tavitar

tavitar

2010-07-06 04:20

reporter   ~0001152

That did it!

Many thanks,
David

Issue History

Date Modified Username Field Change
2010-06-28 04:10 tavitar New Issue
2010-07-05 08:42 greenshift Note Added: 0001147
2010-07-06 04:20 tavitar Note Added: 0001152
2010-07-06 11:16 francis Status new => closed
2010-07-06 11:16 francis Resolution open => fixed