Closed
Bug 1487907
Opened 7 years ago
Closed 7 years ago
lando can't be accessed without Mozilla LDAP
Categories
(Conduit :: Lando, defect)
Conduit
Lando
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ehsan.akhgari, Unassigned)
Details
I had a contributor trying to land a patch with Lando which failed with the following error:
"Unfortunately, you can only login to this website using Mozilla LDAP."
| Reporter | ||
Updated•7 years ago
|
Summary: lando can't be accessed without LDAP → lando can't be accessed without Mozilla LDAP
Comment 1•7 years ago
|
||
This is by design. At this time Lando requires membership in the ldap group required to push to a repository. Users may view the website without ldap, but must have ldap to request landings.
This will be revisited when we have proper policies and machine readable information around code ownership.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Comment 2•7 years ago
|
||
Wow, OK... I would have thought our commit access policy decided who is able to commit to our repositories.
Does this mean that any Mozilla employee can use Lando to land code irrespective of whether they have L3 access?
Flags: needinfo?(smacleod)
Comment 3•7 years ago
|
||
No, it checks the appropriate scm group in LDAP. In mozilla-central's case, this would be (I believe) scm_level_3.
Maybe I'm misunderstanding you, but these LDAP groups are, at the moment anyway, how we implement the Commit Access Policy. Later, we'd like to get finer-grained by having Lando consult a machine-readable version of the module owner & peer definitions, but for now Lando enforces the same controls that hg.mozilla.org does, that is, by consulting LDAP groups.
Flags: needinfo?(smacleod)
| Reporter | ||
Comment 4•7 years ago
|
||
I see, thanks for the explanation! I originally filed this bug based on an incorrect understanding of what had happened but it turns out the true problem was the L3 access of the contributor in comment 0 being deactivated for some reason, which matches perfectly with comment 3. So WONTFIX sounds like the right fix here (or even INVALID but who cares!)
You need to log in
before you can comment on or make changes to this bug.
Description
•