Kontact can't do "simple" LDAP bind

Bug #303328 reported by Rocco Stanzione
2
Affects Status Importance Assigned to Milestone
KDE PIM
Invalid
Medium
kdepim (Ubuntu)
Invalid
Low
Unassigned

Bug Description

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.

Revision history for this message
In , Kde4bugs (kde4bugs) wrote :

Version: kaddressbook 4.1 (using KDE 4.1.2)
OS: Linux
Installed from: Ubuntu Packages

While configuring KAddressbook to access a new company LDAP addressbook, I had problems configuring the authentication.

With Authentication:Simple selected, I could only fill in the "Bind DN" and "Password" fields for my data - The "User" field was grayed out. There were no contacts in the main window at this point.

In order to access the server addressbook, I had to go into the configfile by hand and set the "User" field to the correct value (same as Bind DN), at which point all the contacts appeared correctly.

I guess the "User" field shouldn't be disabled for Simple Authentication, unless I'm missing something.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Thanks for reporting this. It seems this issue is already known upstream. I've added a watch on the upstream bug. Confirmed based on upstream report

Changed in kdepim:
importance: Undecided → Low
status: New → Confirmed
Changed in kdepim:
status: Unknown → New
Revision history for this message
In , Amessina (amessina) wrote :

I confirm this to be a problem in Fedora 10.
See: https://bugzilla.redhat.com/show_bug.cgi?id=474543

Changed in kdepim (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
In , Paulo-fidalgo-pt (paulo-fidalgo-pt) wrote :

You need to have the same user, in user fied, as DC in the Bind DN, at least if you are using an Active Directory.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing in favor of KDE bug.

Changed in kdepim (Ubuntu):
status: Triaged → Invalid
Changed in kdepim:
importance: Unknown → Medium
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Changed in kdepim:
status: New → Incomplete
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Changed in kdepim:
status: Incomplete → New
Revision history for this message
In , Justin Zobel (justin-zobel) wrote :

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Changed in kdepim:
status: New → Incomplete
Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

Changed in kdepim:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.