Closed Bug 1266583 Opened 8 years ago Closed 8 years ago

FxA config for new AMO admin tool

Categories

(Cloud Services :: Operations: Miscellaneous, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mstriemer, Assigned: jbuck)

Details

We are making a new admin tool for AMO and it will be hosted on its own domain, so it needs a new FxA config.

The client id being used on dev (FxA stable) is d884439dc52ee626.

For FxA Prod:

Name: Firefox Add-ons Admin (stage)
Redirect URI: https://addons-admin.stage.mozaws.net/fxa-authenticate

Name: Firefox Add-ons Admin (dev)
Redirect URI: https://addons-admin.prod.mozaws.net/fxa-authenticate

Please send credentials to Jason Thomas.
Noting my approval for the creation of these credentials, with any unspecified config options matching those already in use for addons.mozilla.org
Bump, any progress on these credentials?
I typo'd the original post so here goes again:


Our dev server has client ID d884439dc52ee626 and is pointing at https://stable.dev.lcip.org. We'd like to setup two servers pointing at FxA production:

Name: Firefox Add-ons Admin (stage)
Redirect URI: https://addons-admin.stage.mozaws.net/fxa-authenticate
Note: This is our staging server.

Name: Firefox Add-ons Admin
Redirect URI: https://addons-admin.prod.mozaws.net/fxa-authenticate
Note: This is our production server.
Assignee: nobody → jbuckley
$ curl 'https://oauth.accounts.firefox.com/v1/client/47b542467bb4de6f'
{"id":"47b542467bb4de6f","name":"Firefox Add-ons Admin (stage)","trusted":true,"image_uri":"","redirect_uri":"https://addons-admin.stage.mozaws.net/fxa-authenticate","terms_uri":"","privacy_uri":""}

$ curl 'https://oauth.accounts.firefox.com/v1/client/1120394a0b3e6dc9'
{"id":"1120394a0b3e6dc9","name":"Firefox Add-ons Admin","trusted":true,"image_uri":"","redirect_uri":"https://addons-admin.prod.mozaws.net/fxa-authenticate","terms_uri":"","privacy_uri":""}

I have sent the secrets for both clients to jason. Let me know if any tweaking is needed
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.