Hello everybody !
I work with an Active Directory.
I've installed Ldap Integration module, and when I tried to log in against the AD, I've just : "Sorry. Unrecognized username or password. Have you forgotten your password?"
It is probably a configuration problem.
Here is my configuration :
SERVER SETTINGS
Name : just a name
LDAP Server : I put the IP address
LDAP port : 389
No check on Use start-TLS
No check on Store passwords in encrypted form
LOGIN PROCEDURE
Base DN :
Here I've tested a lot of configuration. I want that all users in this OU can log to the site :
OU=Standard,OU=Users,OU=Office,dc=domain,dc=com
UserName attribute : sAMAccountName
Email attribute : mail
ADVANCED CONFIGURATION :
DN for non-anonymous search : here i've tried an account which have read right and admin right
DN=...,OU=...,CN=...,DC=domain,DC=com
Password for non anonymous search : the password;
Someone can help me ?
Thank you
Comments
Comment #1
jonjonz commentedA bump and I am having a similar problem, same particulars.
Is there any way to tell what is going on. The log just shows a failed password attempt.
Since I have put in a non-anonymous id, I know at least that that part is working because in testing it I have put in the wrong info and gotten an error message reporting the failure to bind and when i put in the correect information, there is no error message regaring the bind.
Given that most or many Drupal implementers are NOT LDAP administrators, it would really be nice if there was some documentation for this module. The remark in the readme file that this is only for LDAP ADMINS is a bit juvenile if you ask me.
In my case it is an Active Directory and I can connect to it using various active directory browsing tools, so I know it is not misbehaving.
This set of modules sort of leaves you hanging since it reveals nothing about why it is not working.
It's a shame that this module seems to be moribund, as I can see where it could be a real deal breaker for a lot of shops where Active Directory has been in place for years.
Comment #2
scafmac commentedTypically things like this tend to be a configuration problem, so I'm changing the status to normal rather than critical. Generally it's considered poor form to give a poor description of your problem or call maintainer's names, but hey everyone has their own style.
Now, let's start with the details:
Jonjonz - Thanks for the juvenile remarks about the juvenile remarks - this module has gotten passed around a fair amount between people who have other jobs, but are willing to contribute what they can. If you are not a programmer, as you noticed the documentation needs work. I would happily accept any documentation improvements or changes you want to provide. Please feel free to contribute something useful like clarifying or correcting outdated or demeaning comments.
If you want help, please provide clear, concise, and sufficient information for the folks that are willing to volunteer their time to help.
Comment #3
tm commentedjust 2 cents...(appreciate having this module around myself, thank you!)
this past issue might help a little: http://drupal.org/node/122641; found the script in comment #1 (by kreaper) useful for troubleshooting.
and thanks again to scafmac for picking up the module; most appreciated!
Comment #4
johnbarclay commentedClosing 5.x issues to clean out issue queue.