Closed
Bug 1421848
Opened 8 years ago
Closed 8 years ago
Have one WebAuthnManager instance per CredentialsContainer
Categories
(Core :: DOM: Device Interfaces, enhancement, P2)
Core
DOM: Device Interfaces
Tracking
()
RESOLVED
INVALID
People
(Reporter: cburnett19922015, Unassigned)
Details
+++ This bug was initially created as a clone of Bug #1421616 +++
We currently have a single WebAuthnManager instance per process, that's shared between all the CredentialContainers. That way the nsPIDOMWindowInner parent has to be tracked by the transaction, as multiple containers could kick off requests simultaneously.
I suggest cleaning this up, so that we have one WebAuthnManager instance per each CredentialsContainer and thus each nsPIDOMWindowInner. Just like U2F has one instance per parent window too.
This simplifies the communication diagram (at least in my head) a little bit, as each U2F/WebAuthnManager instance also has their own TransactionChild for IPC protocol communication. The manager and child are destroyed when the parent window is.
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Updated•8 years ago
|
Resolution: INCOMPLETE → INVALID
Updated•6 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•