Closed
Bug 880292
Opened 11 years ago
Closed 11 years ago
[Contacts] Gmail import is using a personal developer keys
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(blocking-b2g:leo+, b2g18+ fixed, b2g18-v1.0.0 unaffected, b2g18-v1.0.1 unaffected, b2g-v1.1hd fixed)
RESOLVED
FIXED
blocking-b2g | leo+ |
Tracking | Status | |
---|---|---|
b2g18 | + | fixed |
b2g18-v1.0.0 | --- | unaffected |
b2g18-v1.0.1 | --- | unaffected |
b2g-v1.1hd | --- | fixed |
People
(Reporter: arcturus, Assigned: arcturus)
Details
(Whiteboard: [blocking-final-partnerbuild-checklist])
Attachments
(1 file)
We should use a 'mozilla team' keys instead of the personal dev keys used now.
Assignee | ||
Comment 1•11 years ago
|
||
Dylan, James Lal commented me that you could be the person to ask to create those keys under a mozilla team account.
Is that right?
Thanks,
F.
Comment 2•11 years ago
|
||
Yes, we can do that. What API services does the import require?
Flags: needinfo?(francisco.jordano)
Assignee | ||
Comment 3•11 years ago
|
||
Hi Dylan,
Right now we are not asking for any specific api since we are using google contacts api v3:
https://developers.google.com/google-apps/contacts/v3/
that just requires OAuth 2.0 access.
So we will need just the client ids.
Cheers,
F.
Flags: needinfo?(francisco.jordano)
Assignee | ||
Comment 4•11 years ago
|
||
Forgot to mention the rediectus uri's
Redirect URIs: https://serene-cove-3587.herokuapp.com/liveowd/oauth2_new/flow_live.html
JavaScript origins: https://serene-cove-3587.herokuapp.com
Those urls are not hitten by the final user, as we implemented the new Oauth 2.0 redirect mechanism via manifest.
Cheers.
Comment 5•11 years ago
|
||
I created a new key under the Mozilla account and sent it to Francisco. Assigning to him to replace the personal key.
Assignee: nobody → francisco.jordano
Assignee | ||
Comment 6•11 years ago
|
||
Tried on the phone and now when asking for user identity, I got the following developer:
Mozilla Firefox OS
The import working good.
Thanks!
Attachment #760448 -
Flags: review?(jmcf)
Assignee | ||
Comment 7•11 years ago
|
||
Changing to correct flags as the only version affected is 1.1
Asking for leo? since the change risk is minimun and the user impact (asking for credentials coming from Mozilla) is high.
Actually this patch just changes a key id, no code involved here.
Thanks!
F.
blocking-b2g: --- → leo?
status-b2g18:
--- → affected
status-b2g18-v1.0.0:
--- → unaffected
status-b2g18-v1.0.1:
--- → unaffected
status-b2g-v1.1hd:
--- → affected
tracking-b2g18:
--- → +
Updated•11 years ago
|
blocking-b2g: leo? → leo+
Updated•11 years ago
|
Whiteboard: [blocking-final-partnerbuild-checklist]
Updated•11 years ago
|
Attachment #760448 -
Flags: review?(jmcf) → review+
Comment 8•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
Uplifted 9aa39aae3440c1921636253ec62c1ac2d0fde861 to:
v1-train: dfe98487809a226cbcc727ce0a0b90212698af5d
Comment 10•11 years ago
|
||
1.1hd: dfe98487809a226cbcc727ce0a0b90212698af5d
You need to log in
before you can comment on or make changes to this bug.
Description
•