Closed
Bug 1085498
Opened 11 years ago
Closed 10 years ago
Nightly and Aurora loop is using the wrong apiKey
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task, P1)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: msander, Unassigned)
References
Details
(Whiteboard: [qa+])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36
Steps to reproduce:
1. Open the nightly or aurora browser
2. Connect a Loop call
3. Check the apiKey
Actual results:
It's using the apiKey for beta/release so it's connecting to that opentok server environment.
Expected results:
It should use the nightly/aurora key so it can connect to the nightly/aurora server environment.
Comment 1•11 years ago
|
||
OK. Adding some people to look at this right away...
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P1
Whiteboard: [qa+]
Comment 2•10 years ago
|
||
Okay, this is a deployment change, not something in the loop::server component.
Dean, Bob, we need to change the configuration so that we have different keys for different channels.
https://github.com/mozilla-services/loop-server/blob/master/loop/config.js#L204 is the config file, and it should contain a mapping with the different values, per channel.
credentials[channel] should have apiKey and apiSecret defined. I'm not sure where the credentials for the nightly channel are defined, so NI Adam here.
Component: Server → Operations: Deployment Requests
Flags: needinfo?(adam)
Product: Loop → Mozilla Services
Comment 3•10 years ago
|
||
The Nightly / Aurora key is in Bug 1033574. It should be used for both nightly and aurora.
Flags: needinfo?(adam)
Comment 5•10 years ago
|
||
(In reply to James Bonacci [:jbonacci] from comment #4)
> Are there keys (needed) for Beta or Release?
Beta and Release will use the default key that you already have provisioned.
Flags: needinfo?(adam)
Comment 6•10 years ago
|
||
Correction - this is going to get pushed by OPs to Stage and Prod as part of the 0.12.5 release. Should happen this morning and very quickly...
Comment 7•10 years ago
|
||
Corrected/Verified in Loop-Client last week.
Correcting/Verifying in Loop-Stage this week as part of 0.12.5.
Just an FYI...
Comment 8•10 years ago
|
||
Verified Loop-Server Stage and Prod.
This bug can be closed out...
Comment 9•10 years ago
|
||
Closing ticket.
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
•