Opened 4 years ago

Closed 3 years ago

#1486306 closed Bugs (fixed)

LDAP password plugin doesn't allow to bind anonymously

Reported by: ploum Owned by:
Priority: 5 Milestone: 0.4-beta
Component: Plugin API Version: 0.3.1
Severity: normal Keywords: ldap password
Cc:

Description

Sometimes, you don't know the exact DN of an user but you want to bind anonymously so you can look for the user's DN using other fields (like the mail field).

This is done in many LDAP applications like squirrelmail change_ldappass, ejabberd, postfix, …

This should also be possible with the password plugin.

Attachments (2)

anonymous_bind.patch (2.9 KB) - added by ploum 4 years ago.
patch to allow a third method : "anonymous"
anonymous_ldap_bind.patch (3.0 KB) - added by ploum 3 years ago.
Corrected a small error in my previous patch.

Download all attachments as: .zip

Change History (7)

Changed 4 years ago by ploum

patch to allow a third method : "anonymous"

comment:1 Changed 4 years ago by ploum

Currently, on my installation, the above patch provide a blank page after changing the password, I don't know why. I'm not even sure it's related to the patch.

Changed 3 years ago by ploum

Corrected a small error in my previous patch.

comment:2 Changed 3 years ago by ploum

I've been able to test my patch and it works great, at least in my configuration. I think that this patch is pretty safe because the users of non-anonymous method are unlikely to see a difference.

comment:3 Changed 3 years ago by alec

  • Milestone changed from later to 0.4-beta

See also #1486316. Could someone of you review these patches and maybe make a merged one if possible?

comment:4 Changed 3 years ago by ncl

I could be wrong but #1486316 does everything this one does plus allows non-anonymous binds. Where's the point in mering? It's more of a question whether people actually need non-anonymous binds and is it worth adding complexity to the config file if no one will ever use it.

Also some feedback on either of the patches would be really nice. I can only say i haven't encountered any problems with #1486316 in my current setup but that's hardly reliable.

comment:5 Changed 3 years ago by alec

  • Resolution set to fixed
  • Status changed from new to closed

Patch for #1486316 applied in r3472/svn.

Note: See TracTickets for help on using tickets.