Closed Bug 1131781 Opened 9 years ago Closed 9 years ago

Need local settings updated for Fx Accounts testing on stage & dev

Categories

(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jpetto, Assigned: nmaul)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/543] )

We are going to be launching a Firefox Firstrun test for 10% of en-US/Windows users on Thursday 2/12.

One of these tests implements the (rather new) Firefox Accounts relier library[1]. This library requires a unique client ID per domain. The credentials to test from stage (https://www.allizom.org/) and dev (https://www-dev.allizom.org/) are not ready, but should be generated early tomorrow (2/9) at the latest.

The key is in base.py in the WIP branch[2]. Note that only the FXA_RELIER_CLIENT_ID key needs to vary per server. The FXA_RELIER_CONTENT_* URLs will be shared for prod, stage, and dev.

As testing against stage and dev is pretty important, we'd love to get local.py updated on stage and dev tomorrow after the keys have been generated. I know it's a tight window, but can this be accomplished?

[1] - https://github.com/mozilla/fxa-relier-client
[2] - https://github.com/mozilla/bedrock/blob/bug-1128726-fx-firstrun-experiments/bedrock/settings/base.py#L1499
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/543]
Blocks: 1128726
Just to make sure I correctly understand what needs to happen:

I think what you're saying is that you need FXA-related entries to be added to the local.py file for bedrock dev and stage.  A couple of questions:

1) When you say that "FXA_RELIER_CLIENT_ID key needs to vary per server", do you really mean that a) needs to be different on each web-head in dev -or- b) that this key needs to be different between dev, stage, and prod?  ("b" is a lot easier.)

2) Are the credentials already generated and the ID #s available?  (The summary says that the credentials will be "generated early tomorrow (2/9) at the latest".)

Assuming that your answer to question #1 is "b" AND  you still need the push for tomorrow (February 11th), do you know around when you'll need the push done?  That way, we can try to make sure someone is free around that time period.
:cyliang -

1) "b" is correct. The key needs to vary per domain. Apologies for the ambiguity.

2) The IDs have not yet been generated.

:ckolos - Any idea what time the keys will be available? I know generating keys depends on information from webops in bug 1131660, so we're in a bit of a chicken/egg situation...
Flags: needinfo?(ckolos)
keys are created but there's an issue with cyliang's gpg key. I can encrypt for :jakem if needed.
Flags: needinfo?(ckolos)
To bedrock stage, I've updated local.py to include the values below and pushed  out the change.

   FXA_RELIER_CLIENT_ID = '<stage ID from ckolos>'
   FXA_RELIER_CONTENT_HOST = 'https://stable.dev.lcip.org'
   FXA_RELIER_CONTENT_OAUTH = 'https://oauth-stable.dev.lcip.org/v1'

If the URLS should be different from the blob listed in the summary -or- another FXA-related settings is needed, please let me know.  You also find me as "cyliang" on IRC if that is easier. =)
FYI: When I got the key list, there was no specific key listed as being for "dev".  ckolos does not control for creds for the dev oauth, so I don't know if 1) someone else needs to be poked for dev credentials or if 2) the stage client ID I got should be on dev as well.
No longer blocks: 1128726
Depends on: 1131660
:cyliang - 

The creds are being regenerated (see https://bugzilla.mozilla.org/show_bug.cgi?id=1131660#c12). When complete, each server (prod, stage, dev) will need the following local settings (with values replaced, obviously):

FXA_RELIER_CLIENT_ID = '591e9db45a43f7e9'
FXA_RELIER_CONTENT_HOST = 'https://stable.dev.lcip.org'
FXA_RELIER_CONTENT_OAUTH = 'https://oauth-stable.dev.lcip.org/v1'
FXA_RELIER_REDIRECT_URI = 'http://localhost:8000/'
Jakem: cyliang: can we get prod/dev/stage updated Thursday AM? We need to launch the test tomorrow to get enough data by the time Firefox 36 is released. See bug 1131660 for more info.
Flags: needinfo?(nmaul)
Flags: needinfo?(cliang)
I've done a push to dev and stage with the updated client IDS and adding in the FXA_RELIER_REDIRECT_URL.  Can someone verify that it works correctly in those environments before I push to prod?
Flags: needinfo?(nmaul)
Flags: needinfo?(cliang)
Flags: needinfo?(jon)
Flags: needinfo?(chrismore.bugzilla)
Flags: needinfo?(chrismore.bugzilla)
After some back-and-forth in #www, this is completed for www-dev.allizom.org as well as www.allizom.org. We're holding off on prod until a green light.

Here's the settings that prod will get. I've been informed that the client ID is not secret, so I'm pasting it here too just to make this a really easy copy/paste job and so there's no confusion. We do not actually use the "client_secret" setting, so it doesn't appear in the config anywhere.

# Bug 1131781
FXA_RELIER_CLIENT_ID = 'd25b90bb6aec11d7'
FXA_RELIER_CONTENT_HOST = 'https://accounts.firefox.com'
FXA_RELIER_CONTENT_OAUTH = 'https://oauth.accounts.firefox.com/v1'
FXA_RELIER_REDIRECT_URI = 'https://www.mozilla.org/'
Flags: needinfo?(jon)
Pushed to prod after green light in #www.
Assignee: server-ops-webops → nmaul
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.