Please duplicate Lockbox/Lockwise production clientIDs to stage environment
Categories
(Cloud Services :: Server: Firefox Accounts, task)
Tracking
(Not tracked)
People
(Reporter: jrconlin, Unassigned)
Details
We need to test the current Lockwise android client using the Staging environment. The FxA clientID currently being used is e7ce535d93522896
, which is resulting in a client error.
Please duplicate the production clientID sets from production to stage so that we can test.
Comment 1•5 years ago
|
||
As part of this request, could we also ensure the Lockwise iOS client's Production settings are also duplicated to Staging?
The Lockwise iOS clientID is 98adfa37698f255b
. I believe something is there already, but not sure how far from expectations it might have drifted.
Comment 2•5 years ago
|
||
:jrconlin :m_and_m - what should the respective values for redirectUri be for these two ids?
Reporter | ||
Comment 3•5 years ago
|
||
I'm not sure I can answer that. ni'ing :m_and_m
Comment 4•5 years ago
|
||
the redirectUrl's in staging should match what it's set to in production:
- e7ce535d93522896 =>
https://lockbox.firefox.com/fxa/android-redirect.html
- 98adfa37698f255b =>
https://lockbox.firefox.com/fxa/ios-redirect.html
For context, we need to enable the existing clients to work with the staging environment in order to proof out server work. For that, the redirectUrl needs to match what the existing clients expect to use or we'll get 400
errors on mismatched values.
Comment 6•5 years ago
|
||
Done.
$ curl -s https://oauth.stage.mozaws.net/v1/client/e7ce535d93522896 | python -mjson.tool
{
"id": "e7ce535d93522896",
"image_uri": "",
"name": "Firefox Lockwise",
"redirect_uri": "https://lockbox.firefox.com/fxa/android-redirect.html",
"trusted": true
}
$ curl -s https://oauth.stage.mozaws.net/v1/client/98adfa37698f255b | python -mjson.tool
{
"id": "98adfa37698f255b",
"image_uri": "",
"name": "Firefox Lockwise",
"redirect_uri": "https://lockbox.firefox.com/fxa/ios-redirect.html",
"trusted": true
}
$
Let me know if that works for you.
Comment 7•5 years ago
|
||
:jrconlin, :m_and_m - do you want our stage or our stable environment? Stage is normally meant for our internal testing and can go down at any time whereas stable is meant for RPs to test against.
Comment 8•5 years ago
|
||
I believe this is specifically for testing durable sync with different clients, so it needs to happen in stage, and will not be affected by availability concerns.
Description
•