[dashboard][l10n_site] update localizer check for new access policy

RESOLVED FIXED

Status

Mozilla Localizations
Infrastructure
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: Pike, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
We're checking the ldap group for hg_l10n, that's changing to scm_l10n in bug 549873.

Gotta catch up on that fix.
(Reporter)

Updated

8 years ago
Depends on: 549873
(Reporter)

Comment 1

8 years ago
diff --git a/l10n_site/auth/backends.py b/l10n_site/auth/backends.py
--- a/l10n_site/auth/backends.py
+++ b/l10n_site/auth/backends.py
@@ -120,6 +120,6 @@
             self.ldo = ldap.initialize(self.host)
             self.ldo.set_option(ldap.OPT_PROTOCOL_VERSION, 3)
             self.ldo.simple_bind_s(self.dn, self.password)
-            self.localizers = self.ldo.search_s("ou=groups,dc=mozilla", ldap.SCOPE_SUBTREE, "cn=hg_l10n")
+            self.localizers = self.ldo.search_s("ou=groups,dc=mozilla", ldap.SCOPE_SUBTREE, "cn=scm_l10n")
             self.ldo.unbind_s()
         return username in self.localizers[0][1]['memberUid']

works, I'll land a patch in hg after breakfast. Right now, it's just locally patched
(Reporter)

Comment 2

8 years ago
http://hg.mozilla.org/l10n/django-site/rev/702d14941fcd, FIXED.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.