Closed DessaiImrane closed 11 years ago
Some explanation :
AD authorizes "anonymous" bind So, a DN without no password is equivalent to Unauthenticated Bind And a DN with a wrong password is NOT a Anonymous Bind
Bind doesn't necesserly grant read access on ldap. You have to have the rights to do so.
Many solutions :
Many other projects got the same problem (ie redmine) Google search : ad bind empty password
FYI : It is in the file "module/module.py", l249
Which solution do you prefer ?
? I already fix this in the sources since months (password == '' -> drop).
On Fri, Aug 23, 2013 at 7:30 AM, DessaiImrane notifications@github.comwrote:
Some explanation :
AD authorizes "anonymous" bind So, a DN without no password is equivalent to Anonymous Bind And a DN with a wrong password is NOT a Anonymous Bind
Bind doesn't necesserly grant read access on ldap. You have to have the rights to do so.
Many solutions :
- Disabled Anonymous Bind in AD (not recommended according to some sources)
- Making this module more stronger -- Checking if password is "empty" beofre making the bind
Many other projects got the same problem (ie redmine) Google search : ad bind empty password
FYI : It is in the file "module/module.py", l249
Which solution do you prefer ?
— Reply to this email directly or view it on GitHubhttps://github.com/shinken-monitoring/mod-auth-active-directory/issues/3#issuecomment-23144266 .
pfff ! I'm sorry, I miss read the source code.
I close this issue
:p
On Fri, Aug 23, 2013 at 9:22 AM, DessaiImrane notifications@github.comwrote:
pfff ! I'm sorry, I miss read the source code.
I close this issue
— Reply to this email directly or view it on GitHubhttps://github.com/shinken-monitoring/mod-auth-active-directory/issues/3#issuecomment-23147543 .
Hi,
I'm using this module to auth my users on WebUI (against an Active Directory)
Giving a wrong username or a wrong password will make auth failed (expected behavior)
Giving a right username with empty password will make auth success (huhu not expected behavior, of course)
Maybe a problem with the filter in the ldap query ?