Commit Access (Level 1) for James Jahns
Categories
(Infrastructure & Operations :: Infrastructure: LDAP, enhancement)
Tracking
(Not tracked)
People
(Reporter: jahnsjam, Unassigned)
Details
Attachments
(1 file)
743 bytes,
application/vnd.ms-publisher
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
email: jahnsjam@msu.edu
(MSU Capstone student)
I have read, and agree to abide by, the Commit Access Requirements.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Hey James - you definitely want / need Level 1 and not Level 3. :) I'll go ahead and update the bug.
Comment 2•6 years ago
|
||
I can vouch for James for L1 commit access - he's an MSU student we're working with.
Comment 3•6 years ago
|
||
Mike has vouched so clearing ni.
Comment 4•6 years ago
|
||
Over to Infra to create the L1 account.
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Hello,
Password has been sent via provided email. +LDAP, +SSH key, +HG, +level_1.
Please confirm when you have access so we can resolve this bug.
Thank you.
Reporter | ||
Comment 6•6 years ago
|
||
Access confirmed, you can close. Thanks!
Updated•6 years ago
|
Comment 7•6 years ago
|
||
On IRC, James posted that he's having trouble using ./mach try
, and the output of ssh hg.mozilla.org
included:
A SSH connection has been established and your account (jahnsjam@msu.edu)
was found in LDAP.
However, Mercurial access is not currently enabled on your LDAP account.
Please follow the instructions at the following URL to gain Mercurial access:
This was surprising to me - it implies the SSH connection worked, but somehow the SSH key and account don't have the relevant permissions. Is it possible one of the LDAP bits (scm_level_1, maybe?) is still missing?
Comment 8•6 years ago
|
||
Hi James. We have disabled and re-enabled HG access. Please sign out and sign back in to test and let us know the results. Thank you.
Reporter | ||
Comment 9•6 years ago
|
||
(In reply to Mike Poessy [:mpoessy] from comment #8)
Hi James. We have disabled and re-enabled HG access. Please sign out and sign back in to test and let us know the results. Thank you.
That fixed the issue, thanks!
Description
•