Closed
Bug 1027403
Opened 10 years ago
Closed 10 years ago
Generate FindMyDevice secrets and URIs for OAuth PROD
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: edwong, Unassigned)
References
Details
2) Define client data in this format for each partner in each env (dev/stage/prod) { id: "(16 bit client id)", secret: "(64 bit secret)", name: "(client name)", imageUri: "(https://some-url)", redirectUri: "(http://some-url)", whitelisted: (true/false) } 3) These values, once generated, will be considered secret and not available in the general puppet repository. For this reason, svcops folk will have to maintain this list. (for now? forever?) Also, any changes to this data after it is written to the DB must be done from an fxa-db-write instance/account in RDS. Once these are done, we can setup a reliable prod-stack for oauth/profile
Reporter | ||
Updated•10 years ago
|
No longer blocks: 1027278
Summary: Generate secrets for FindMyDevice and provide OAuth URIs for PROD → Generate FindMyDevice secrets and URIs for OAuth PROD
Secrets have been generated and saved in puppet.
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
•