Closed
Bug 802744
Opened 13 years ago
Closed 12 years ago
Cutover production browserid to new identity specific socketlabs account
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gene, Assigned: gene)
Details
Update the credentials used for socketlabs here
svn.mozilla.org/sysadmins/puppet/weave/modules/browserid/manifests/swebhead.pp
based on the new creds here :
svn.mozilla.org/sysadmins/gpg/services/passwords.txt.gpg
Force a puppet run, test production
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → gene
Comment 1•12 years ago
|
||
Hey, are we using the new credentials in production/stage now?
Comment 2•12 years ago
|
||
Just logged into socketlabs while trying to debug a personatestuser thing, nope we're not.
It would be ideal to switch this over prior to next week's possible partner announcement, so that socketlabs can prep their internal network to handle a possible explosion of throughput.
Comment 3•12 years ago
|
||
Note: to pick up a change to config will require a restart of at least dbwriter.
Assignee | ||
Comment 4•12 years ago
|
||
Change is coded and ready to deploy at 1pm today.
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•12 years ago
|
||
SCL2 is updated
Assignee | ||
Comment 6•12 years ago
|
||
reverted the change after discovering auth was failing. root cause, there is a different user/pass for smtp auth than for user auth. I had configured it using the svcops user account username and pass
Assignee | ||
Comment 7•12 years ago
|
||
Pushed out the corrected credentials and tested this is working on the new account.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•