#820: Web Authentication: Large Blob extension
Discussions
2023-04-tokyo
We have questions:
- The explainer talks about a 'small amount of data', why is this called 'largeBlob'?
- Why is it called a blob if it's reading and writing array buffers? The property name should be relevant to the data type, either make the API accept a Blob or use a name that doesn't imply Blobs.
- What's the size limit of the data? If there any way for the RP to know what's available?
- Is there expected to be a mechanism for the user to clear this data? (Independent of clearing the entire auth for the RP) Either via UA UI or a future API call?
Posted questions to the issue.
2023-07-mos-eisley
Dan: good multi-stakeholder signals - it's shipped - although Chromestatus doesn't reflect the multistakeholder support. We left feedback in Tokyo - no response.
Amy: they may need a nudge? [leaves comment]
2023-08-14
Peter: naming is unfortunate. It's not large and it's not a blob. Other than that okay. Has shipped. Apple are using it.
OpenedFeb 21, 2023
Salutations TAG!
I'm requesting a TAG review of the Web Authentication Large Blob extension.
The Web Authentication Large Blob extension allows relying parties to store small amounts of opaque data associated with a credential on an authenticator. This is useful for authentication schemes involving storing certificates on authenticators.
large-blob
files).Further details:
You should also know that...
This feature requires OS-level support for platforms where the OS handles WebAuthn requests (this is the case for Windows). Support on Windows has already shipped.
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @nsatragno