Closed
Bug 912219
Opened 11 years ago
Closed 11 years ago
Generate Hawk headers using Sync 2.0 token from FxAccounts module
Categories
(Firefox :: Sync, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: zaach, Assigned: zaach)
References
Details
(Whiteboard: [qa+])
The FxAccounts module can expose a method for generating Hawk authorization headers, which rely on the Sync 2.0 token it has stored.
|
||
Updated•11 years ago
|
Whiteboard: [qa+]
|
||
Comment 1•11 years ago
|
||
Alternative API is to have the FxAccounts module expose an interface to get the token, and the Hawk auth header generation can happen in identity.js. I think that's better, but I could be swayed.
|
||
Comment 2•11 years ago
|
||
Generally, pass as little between compartments as possible. Given that some Hawk headers require reading the request body, I'd go with Chris's approach in Comment 1. Generally I feel like that's a smoother API, too.
|
Assignee | |
Comment 3•11 years ago
|
||
Yeah, let's keep Hawk out of the FxA module.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
|
||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•