Closed Bug 1143676 Opened 10 years ago Closed 10 years ago

[ldap] MozLdapBackend has nothing to do with REMOTE_USER and auth on the server side

Categories

(Webtools Graveyard :: Elmo, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

References

Details

Attachments

(1 file)

Seems we got the "remote" part of RemoteUserBackend wrong back in the days. Gotta drop that mistake to update django to a current version, as they tightened their handling of the REMOTE_USER META, which we never set. Rightfully so.
Peter, hitting you with yet another review request. We never were REMOTE_USER, and with https://github.com/django/django/commit/c9e3b9949cd55f090591fbdc4a114fcb8368b6d9 and 1.4.14, our tests broke.
Assignee: nobody → l10n
Attachment #8578037 - Flags: review?(peterbe)
Attachment #8578037 - Flags: review?(peterbe) → review+
Commit pushed to develop at https://github.com/mozilla/elmo https://github.com/mozilla/elmo/commit/ae025e1fc375353e4415ea1a23cb44ab1210c7fc bug 1143676, our ldap backend is not remote, r=peterbe This is really fixing a misunderstanding from back in the days. We were never a REMOTE_USER backend on the apache front or something. Just stop pretending we are.
This is on dev, marking FIXED.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: