Closed
Bug 1090654
Opened 10 years ago
Closed 10 years ago
Changes to prod and stage FxA Oauth configs for Marketplace
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ckarlof, Unassigned)
Details
We need some changes to the FxA OAuth configs for Marketplace in prod and stage.
https://github.com/mozilla/fxa-dev/issues/77
Reporter | ||
Comment 1•10 years ago
|
||
Mark, can you confirm the details here? I believe these are just changes to the redirect URIs:
Stage: https://marketplace.allizom.org/fxa-authorize
Production: https://marketplace.firefox.com/fxa-authorize
but can you provide the client_id for the configs that need changing?
Flags: needinfo?(mstriemer)
Comment 2•10 years ago
|
||
Stage:
"name": "Firefox Marketplace Stage",
"imageUri": "https://marketplace-stage.cdn.mozilla.net/media/img/mkt/logos/128.png",
"redirectUri": "https://marketplace.allizom.org/fxa-authorize",
Stage payments:
"name": "Marketplace Payments Stage",
"imageUri": "https://marketplace-stage.cdn.mozilla.net/media/img/mkt/logos/128.png",
"redirectUri": "https://marketplace.allizom.org/mozpay/spa/fxa-auth",
Production:
"name": "Firefox Marketplace",
"imageUri": "https://marketplace.cdn.mozilla.net/media/img/mkt/logos/128.png",
"redirectUri": "https://marketplace.firefox.com/fxa-authorize",
Production payments:
"name": "Marketplace Payments",
"imageUri": "https://marketplace.cdn.mozilla.net/media/img/mkt/logos/128.png",
"redirectUri": "https://marketplace.firefox.com/mozpay/spa/fxa-auth",
We'll need to set payments as well, I think this is all the information we need to provide other than the client_id.
We store the client_id in our private config, is it okay for me to post it publicly? I think it gets included in the OAuth request but I just want to be sure.
Flags: needinfo?(mstriemer) → needinfo?(ckarlof)
Comment 3•10 years ago
|
||
I went looking for the stage client_ids and we are using the client_id for local development on stage. This makes me wonder if all the client_ids and secrets have been setup. How do we go about getting that setup?
Reporter | ||
Comment 4•10 years ago
|
||
FWIW, we're not using the imageUris currently, but it will be good to have them for the future.
Flags: needinfo?(ckarlof)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(ckarlof)
Reporter | ||
Comment 5•10 years ago
|
||
> We store the client_id in our private config, is it okay for me to post it publicly? I think it gets included in the OAuth request but I just want to be sure.
Correct, client_id is not intended to be secret.
Reporter | ||
Comment 6•10 years ago
|
||
Thanks ckolos! I can see the changes reflected in prod. Can you please put the client_ids for the four reliers you provisioned/edited here in this bug?
Flags: needinfo?(ckarlof) → needinfo?(ckolos)
:jason has been sent the creds and the prod db has been updated
Marketplace Payments Stage
ClientID: e39e5fe5d3ed5529
--
Marketplace Payments
ClientID: 6e842991a9c06f4b
--
Firefox Marketplace Stage
ClientID: 85d69c6e30b5e52d
--
Firefox Marketplace
ClientID: 0a42ac8a73be8762
Flags: needinfo?(ckolos)
Reporter | ||
Updated•10 years ago
|
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
•