Closed
Bug 1300101
Opened 9 years ago
Closed 9 years ago
new ldap account for "balrogagent"
Categories
(Infrastructure & Operations :: Infrastructure: LDAP, task)
Infrastructure & Operations
Infrastructure: LDAP
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
References
Details
I'm going to be deploying bug 1246675 in the coming weeks, and the production deployment will need a new LDAP account in order to auth to the Balrog admin app. I'd like this new account be named "balrogagent", and given access to the Balrog prod interface.
It will need a password set in order to do http auth. Let me know if you want me to generate one, or if you want to do it and send it to me.
Updated•9 years ago
|
Assignee: nobody → infra
Component: MOC: Service Requests → Infrastructure: LDAP
QA Contact: lypulong
Reporter | ||
Comment 1•9 years ago
|
||
Benson tells me that the way we're deploying this shouldn't require an LDAP account, so I'm closing this. Sorry for the noise!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•