Public bug reported:

Binary package hint: kdepim

If I configure an LDAP resource with simple authentication, the only
field to enter the binddn is the "Bind DN" field, which makes sense,
only it doesn't seem to have any effect for simple authentication.  In
previous (3.x) versions of KDE, I counterintuitively had to enter the
binddn in the "User" field for this to work.  In Intrepid, that still
seems to be necessary, only the User field is unavailable if you select
simple authentication.  To make it work I had to select SASL, copy the
binddn into the (now available) User field, re-select Simple, and save.
It took a lot of frustration before trying something as ridiculous as
that.  I wouldn't think this should be too hard to fix.

A little more information might help:

With the binddn in the "Bind DN" field, I could see in my openldap logs
that the binddn used for the connection was "", i.e. none, and any
attempt to write to the LDAP resource generated an error log on the
server (but no indication of failure in Kontact) that modifications
require authentication.  The new contact (if that's what I was trying)
would appear in the address book, even though the LDAP connection was
the only configured resource and it failed.  When I would restart
Kontact, the new entry would be gone.

So I put the binddn in the User field, working around the UI to do so,
and now it works just fine.

** Affects: kdepim (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Kontact can't do "simple" LDAP bind
https://bugs.launchpad.net/bugs/303328
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to