LDAP Authentication does not work

RESOLVED FIXED

Status

Webtools Graveyard
Verbatim
RESOLVED FIXED
9 years ago
2 years ago

People

(Reporter: wenzel, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

9 years ago
After svn upping Verbatim Alpha, logging in via LDAP does not work anymore. I just get "Your username and password didn't match. Please try again.".

I have not changed any settings.

Is there a way to debug this, Wil? The log file does not seem to have been written at all, which makes me think the LDAP component is not hooked up anymore.
(Reporter)

Updated

9 years ago
Blocks: 502215
the LDAP stuff is all contained in that one auth file.  Make sure logging is enabled and writable?

After that I'd just start digging into that file.  Also, you're using the right user/pass to bind to ldap, right?
(Reporter)

Comment 2

9 years ago
Yup, if the credentials haven't changed, I am using the right ones. I'll dig into it, thanks :) Having logging enabled and working seems like a good idea in general, even for other parts of the code.
(Reporter)

Comment 3

9 years ago
Quick update:
- logging reintroduced
- updated the way outdated settings.py with new defaults
- set up Apache correctly

now: making Django find the ldap auth module again.
btw. you may find it useful. For our l10n django dashboard I wrote LDAP django backend that works similarly to Will's code, but supports ldaps. I can confirm that the code works.

http://hg.mozilla.org/users/axel_mozilla.com/django-site/file/tip/l10n_site/auth/backends.py
(Reporter)

Comment 5

9 years ago
nice, maybe we should get that upstream some time, LDAPS would certainly be an improvement -- though none of the Pootle guys probably has such a server to test ;).
(In reply to comment #5)
> nice, maybe we should get that upstream some time, LDAPS would certainly be an
> improvement -- though none of the Pootle guys probably has such a server to
> test ;).

Last I knew we're the only people doing anything with LDAP - they don't test it at all (but it worked when I left it).
(Reporter)

Comment 7

9 years ago
Oh, I'm sure I'll be able to hook it up again -- the entire directory structure changed though, so I have to move things around a little bit.
(Reporter)

Comment 8

9 years ago
Now it works again, though I needed to file an upstream bug to get the default settings file adjusted: http://bugs.locamotion.org/show_bug.cgi?id=1023 .

Now when I log in with LDAP (woot), I am taken to: https://sm-cms01.mozilla.com:8081/accounts/fwenzel%40mozilla.com/ which is a 404. http://bugs.locamotion.org/show_bug.cgi?id=1024
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED

Comment 9

9 years ago
(In reply to comment #6)
> (In reply to comment #5)
> > nice, maybe we should get that upstream some time, LDAPS would certainly be an
> > improvement -- though none of the Pootle guys probably has such a server to
> > test ;).
> 
> Last I knew we're the only people doing anything with LDAP - they don't test it
> at all (but it worked when I left it).

If you are able to build tests it may help to ensure that other Pootle work doesn't break the LDAP functionality.  You r call on whether its a good use of time as apposed to fixing errors as they're identified.
(Assignee)

Updated

2 years ago
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.