1488838 - Add ADM keys for Stage & Production

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Operations: Autopush, task)

Description

[JR Conlin [:jrconlin,:jconlin]]

ADM keys have been requested from the fire-tv project:

https://github.com/mozilla-mobile/firefox-tv/issues/1065

This bug serves as a tracking bug for ops.

Comment 1

[Jeremy Orem [:oremj]]

Is this still needed?

Comment 2

[JR Conlin [:jrconlin,:jconlin]]

The ADM work appears to have been de-prioritized. I'm fine with this being closed for now.

Comment 3

[JR Conlin [:jrconlin,:jconlin]]

will re-open when ADM work reprioritized.

Comment 4

[Chenxia Liu [:liuche]]

We'll be using ADM for FxA AutoPush now in Q3, so I'm going to re-open this.

Let me know how I should send the credentials over.

Comment 5

[Jeremy Orem [:oremj]]

What needs to be done here?

Comment 6

[JR Conlin [:jrconlin,:jconlin]]

Whoever controls the Amazon App needs to get the API credentials.

https://developer.amazon.com/docs/adm/obtain-credentials.html#getting-your-oauth-credentials-and-api-key

Once you have those, they can be installed into .autopush_endpoint.ini as adm_creds (or the ADM_CREDS env var as)

{"profile":{"app_id":"...", "client_id":"...", "client_secret"::"..."}}

where profile is the profile group (similar to how iOS profiles work, with "dev", "stage", "prod", etc.)

Comment 7

[Jeremy Orem [:oremj]]

liuche, can you contact me on slack (oremj) and we can arrange the transfer?

Comment 8

[Chenxia Liu [:liuche]]

I'm not working on this but I will ask the assignee to ping you on slack to transfer them.

Comment 9

[Jeremy Orem [:oremj]]

darcese has transferred credentials to me. What should the app_id be? I have the client id and secret. Should it be the same for dev/stage/prod?

Comment 10

[JR Conlin [:jrconlin,:jconlin]]

AppId should be determined by the devs implementing the ADM receiver client.

The AppID identifies which (if any) key set should be used for this bridge connection. (See the bridge interface documentation for details). If there is no distinction between the various apps, then a common AppID could be used.

Comment 11

[Chenxia Liu [:liuche]]

We do want this app id to be different from the common AppID (because we care about how many users are using Sync on FFTV), but I'm not clear on if additionally a separate debug app id (for example) would mess with what FxA uses different clients for. Probably firefox-fire-tv as the id name, but it'd be helpful to know how else App Services uses this id.

Comment 12

[Ryan Kelly [:rfkelly]]

I don't believe we use it for anything else, so using a separate app id here shouldn't interfere with anything FxA or Sync is doing (IIUC of course).

Comment 13

[Chenxia Liu [:liuche]]

Okay, let's go with "firefox-fire-tv". Sorry for the delay!

Comment 14

[Jeremy Orem [:oremj]]

Should these be deployed to autopush stage, prod or both?

Comment 15

[JR Conlin [:jrconlin,:jconlin]]

I would presume "both" since it's probably easiest to have fire-tv point to prod than the stage push boxes. I don't see a problem with traffic load on prod for this.

Comment 16

[Jeremy Orem [:oremj]]

This has been deployed to stage, profile is "fftv" app_id is firefox-fire-tv. Let me know when I should deploy to prod.

Comment 17

[Chenxia Liu [:liuche]]

I think we can do prod now - we're incorporating ADM already in this bug: https://github.com/mozilla-mobile/firefox-tv/issues/2527

and there won't be very much load at all.

Comment 18

[Chenxia Liu [:liuche]]

Hey Jeremy, just wanted to make sure you saw this - we're good to push to prod, unless there are reasons on the infrastructure side that would mean we shouldn't? And then we can close this bug.
And just to confirm, is there a different endpoint between prod/stage from https://updates-push.services.mozaws.net/push/ ?
Thanks!

Comment 19

[Jeremy Orem [:oremj]]

This has been pushed to prod. Yes the endpoint in comment 18 should be correct.

Comment 20

[Jeremy Orem [:oremj]]

Sorry, I misread comment 18. The domain name for prod is updates.push.services.mozilla.com