Closed Bug 903123 Opened 11 years ago Closed 11 years ago

Implement Hawk authentication header provider for Android Background Services

Categories

(Android Background Services Graveyard :: Crypto, defect)

Product:
Android Background Services Graveyard
Component:
Crypto
Platform:
All
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Firefox 26

People

(Reporter: nalexander, Assigned: nalexander)

References

(
URL
)

Details

(Whiteboard: [qa-]) 

The slated Firefox Account/PICL authentication protocol authenticates using Hawk (https://github.com/hueniverse/hawk).  The Hawk protocol is not well specced, but it is pretty easy to implement against the current Node.js code.  This ticket tracks implementing a Java AuthHeaderProvider that speaks the Hawk protocol.

This is similar in spirit to Bug 799729, which did the same for the MAC Auth protocol that Hawk supercedes.
Over to rnewman for review.  We could land this on m-c or elm.
URL: https://github.com/mozilla-services/a...
Flags: needinfo?(rnewman)
f+, but a few testability/reuse/perf questions.
Status: NEW → ASSIGNED
Flags: needinfo?(rnewman)
Also: m-c. Upstream everything we can.
Review comments pushed to github.
Flags: needinfo?(rnewman)
r+ in git.
Flags: needinfo?(rnewman)
https://hg.mozilla.org/mozilla-central/rev/b18e202de776
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Is there anything that the Android QA teams needs to do/test/track for this?
Whiteboard: [qa?]
Nope, any issues will be caught when we start building the Android storage client.
Whiteboard: [qa?] → [qa-]
You need to log in before you can comment on or make changes to this bug.