View Issue Details

IDProjectCategoryView StatusLast Update
0001995SOGoBackend Generalpublic2012-11-21 11:25
Reportersebblin Assigned To 
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionno change required 
Product Versionnightly v2 
Summary0001995: error connection LDAP
Description

I use LDAP service on port 390, it works as shown below :


root@debian6# ldapsearch -h 127.0.0.1 -p 390 -D "cn=admin,dc=test,dc=asso" -w Secret

extended LDIF

#

LDAPv3

base <> (default) with scope subtree

filter: (objectclass=*)

requesting: ALL

#

search result

search: 2
result: 32 No such object

numResponses: 1


By against the LDAP connection fails SOGo, as shown below :


LDAP Access

Failed: Simple Bind Failed: NT_STATUS_LOGON_FAILURE

This is the code. GNUstepDefaults :

<dict>
<key>CNFieldName</key>
<string>cn</string>
<key>IDFieldName</key>
<string>uid</string>
<key>UIDFieldName</key>
<string>uid</string>
<key>baseDN</key>
<string>ou=users,dc=test,dc=asso</string>
<key>bindDN</key>
<string>cn=admin,dc=test,dc=asso</string>
<key>bindPassword</key>
<string>Secret</string>
<key>canAuthenticate</key>
<string>YES</string>
<key>displayName</key>
<string>contact</string>
<key>hostname</key>
<string>127.0.0.1</string>
<key>id</key>
<string>ldap</string>
<key>isAddressBook</key>
<string>YES</string>
<key>passwordPolicy</key>
<string>NO</string>
<key>port</key>
<string>390</string>
<key>scope</key>
<string>SUB</string>
<key>type</key>
<string>ldap</string>
</dict>

if i type it without specifying the LDAP port number.


root@debian6# ldapsearch -h 127.0.0.1 -D "cn=admin,dc=test,dc=asso" -w Secret

I have the same message as returned by SOGo.

ldap_bind: Invalid credentials (49)
additional info: Simple Bind Failed: NT_STATUS_LOGON_FAILURE

Is this a bug sogo ? Is it ignores the port number in the configuration .GNUstepDefaults ?

Additional Information

Knowing that I test SOGo v2.0.0 RC5 (Version: 2.0.0.20120925-1) on a Debian squeeze on Virtualbox.

TagsNo tags attached.

Activities

ludovic

ludovic

2012-11-20 17:21

administrator   ~0004940

The port parameter works, as it's being used in the ZEG version which has native Outlook support (we use 3389).

Do you still have the issue? Have you tried sniffing on port 389/390?

sebblin

sebblin

2012-11-21 09:39

reporter   ~0004945

I reinstalled SOGo with "apt-get install sogo --reinstall", and it fixed the problem.

Before migrating SOGo v1 to v2, I migrated "Debian 5" to "Debian 6" may be the cause of the bug!?

I think this bug can be closed.

Issue History

Date Modified Username Field Change
2012-09-26 13:51 sebblin New Issue
2012-11-20 17:21 ludovic Note Added: 0004940
2012-11-21 09:39 sebblin Note Added: 0004945
2012-11-21 11:25 ludovic Status new => closed
2012-11-21 11:25 ludovic Resolution open => no change required