Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
I know my LDAPURL, user, password and binding works, as I've tried it on the command line with ldapsearch
The interesting thing is when I attempt to access the site, I get the user/pass dialog and it asks for my username and pass 3 times before exiting to the 'Authorization Required' page. However, no errors are thrown in the logs. If I enter a bad username or a bad password, then I get the expected error in the log.
So it's as if LDAP authentication is working, but apache continues to block access. Is there something I'm missing here?
is anything showing up in the apache logs about the ldap errors on on the dc you are authenticating against?
I think the standard way to list the auth user is
AuthLDAPBindDN "cn=helpdesk,dn=someplace,dc=domain,dc=com"
I have to do it the same way you have but have been told that is a non-standard way to connect to AD. everything else looks good compared to my configs.
5 min before I left work, I did what it said and seems to work but I need to check that my result is OK.
- for example reading the links I have given her: at the present time, I believe theory backs up results
UPDATE: is working
AuthBasicProvider ldap
# authenticate only, send authorization to some other system (authz_user cos of valid-user?), as yet not fully understood
AuthzLDAPAuthoritative off
# if authenticates, then authorized
Require valid-user
(The object of using ldap is, of course, to relieve me of users and free me from audits for programs like nagios, NeDi, cati, "home made" etc etc etc)
I am using Suse 10 and IE
/mvh Owen Brotherwood, Denmark
Quote:
Originally Posted by vortmax
The interesting thing is when I attempt to access the site, I get the user/pass dialog and it asks for my username and pass 3 times before exiting to the 'Authorization Required' page. However, no errors are thrown in the logs. If I enter a bad username or a bad password, then I get the expected error in the log.
So it's as if LDAP authentication is working, but apache continues to block access. Is there something I'm missing here?
adding the AuthzLDAPAuthoritative off did it. I could of sworn that I tried it with that line in there before though...then again I tried so many configurations it's hard to tell.
Now... does anyone know anything about caching? I saw some stuff when I was trying to just get it to work but didn't pursue it.
A Newbie's Getting Started Guide to Linux
Learn the basics of the Linux operating systems. Get to know what it is all about, and familiarize yourself with the practical side. Basically, if you're a complete Linux newbie and looking for a quick and easy guide to get you started this is it. subscribe
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe