Closed
Bug 1301332
Opened 9 years ago
Closed 9 years ago
Becoming a Firefox Account Relier for Kinto-Webextensions
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rhubscher, Unassigned)
Details
In order to use the new chrome.storage.sync webextension feature and to try it in Nightly we would need to have `client_id` and `client_secret` credentials on both the stage and the prod FxA stack.
Our current `client_id` for dev is: 88dfc7a5545c6129
The requested scope to be used will be: `sync:addon-storage`
Thanks
Comment 1•9 years ago
|
||
What application will hold these credentials? I was under the impression that the chrome.storage.sync code was landing in Firefox itself and could re-use the existing Firefox client_id.
Flags: needinfo?(rhubscher)
| Reporter | ||
Comment 2•9 years ago
|
||
On the Kinto side we are using the client_id and client_secret to validate the token have been issued for this app. What should I configure then?
Flags: needinfo?(rhubscher)
Comment 3•9 years ago
|
||
IIUC you shouldn't need a client_secret just for verifying the tokens. Is the server checking that the token was issued to a specific client_id?
| Reporter | ||
Comment 4•9 years ago
|
||
Apparently it is when we use the server as a relier but for this specific use case we won't so I will close this and we will use the Firefox client_id.
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
•