Updating browser id to use the new permission manager api

RESOLVED FIXED in mozilla17

Status

()

Core
Identity
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: mounir, Assigned: mounir)

Tracking

(Blocks: 1 bug)

Trunk
mozilla17
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-basecamp:+)

Details

(Whiteboard: [qa-])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 644152 [details] [diff] [review]
Patch

Jonas, feel free to redirect the review to a BrowserID peer (if such thing exist) if you don't feel comfortable reviewing that.
Attachment #644152 - Flags: review?(jonas)
Attachment #644152 - Flags: review?(jonas) → review+
blocking-basecamp: --- → +
https://hg.mozilla.org/mozilla-central/rev/d60807c526a5
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Mounir, Jonas: can you explain what this change does?
(Assignee)

Comment 3

5 years ago
Instead of using the permission manager using an URI, this code is using the permission manager using a principal, which carries more information than an URI. The idea is to have at some point, when all consumers of the permission manager will be changed, to have the permission manager using the principal's appid.

Updated

5 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.