Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bit set by the SPC extension should backed up as part of the Public Key Credential Source #2153

Open
timcappalli opened this issue Sep 25, 2024 · 2 comments
Assignees
Labels
@Risk Items that are at risk for L3 type:technical

Comments

@timcappalli
Copy link
Member

PLACEHOLDER

Proposed Change

Bit set by the SPC extension should backed up as part of the Public Key Credential Source.

@selfissued
Copy link
Contributor

This makes sense to me.

@dwaite
Copy link
Contributor

dwaite commented Oct 23, 2024

Suggest altering the definition of credential source to say that extensions supplied during creation can define their own additional data, e.g.

A credential source ([CREDENTIAL-MANAGEMENT-1]) used by an authenticator to generate authentication assertions. A public key credential source consists of a struct with will contain the following items:

and at the end

Extensions supplied during the authenticatorMakeCredential operation MAY define additional data as part of the credential source.

This would give a path for SPC to define what information needs to be retained to differentiate the credential separately.

@nadalin nadalin added the @Risk Items that are at risk for L3 label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@Risk Items that are at risk for L3 type:technical
Projects
None yet
Development

No branches or pull requests

4 participants