Closed
Bug 1124859
Opened 10 years ago
Closed 10 years ago
hala.metrics.scl3: PAM/LDAP issue for user rweiss
Categories
(Infrastructure & Operations :: Infrastructure: Puppet, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joy, Assigned: jabba)
Details
Hello
The rstudio server works nicely for existing users (server can be found here: http://hala.metrics.scl3.mozilla.com:8787/)
Howeve Rebecca Weiss joined us recently and though her LDAP works on other machines, rstudio does not log her in.
What could be the issue?
Reporter | ||
Comment 1•10 years ago
|
||
Oh, and that server sits behinds the VPN.
Assignee | ||
Comment 2•10 years ago
|
||
I'm not familiar with rstudio. How is its authentication configured? Does the app use LDAP for authentication and authorization, or does it use its own internal user database? You mention PAM in the summary, so maybe it uses local unix authentication? Please provide more information and we can narrow down where the problem is.
Thanks.
Comment 3•10 years ago
|
||
joy said to me that it used LDAP for auth, but he will have to confirm that.
Comment 4•10 years ago
|
||
confirmed with joy that auth is LDAP
Assignee | ||
Comment 5•10 years ago
|
||
I looked at /var/log/secure and saw lots of error messages relating to a missing library, fprintd-pam, so I installed that. Then upon further investigation, I noticed it expects uid, rather than mail for authentication. Try logging in with 'rweiss' and your LDAP password, rather than the e-mail address.
Comment 7•10 years ago
|
||
Just tried with 'rweiss' and LDAP password, still no joy.
Note that I am behind VPN and that this is not the error message e.g. wrong password or login. I submit my credentials and the page just seems to refresh.
Flags: needinfo?(rweiss)
Comment 8•10 years ago
|
||
Was able to log in via Chrome; I'll have to see if there's something going on with my Firefox plug-ins. Consider resolved.
Assignee | ||
Updated•10 years ago
|
Assignee: infra → jdow
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•