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

Add BE/BS steps to authData generation #2141

Merged
merged 3 commits into from
Sep 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -4758,6 +4758,14 @@ the requested [=public key credential|credential=] is [=scoped=] to exactly matc
possibly combined in a single [=authorization gesture=],
then the authenticator will set both the [=UP=] [=flag=] and the [=authData/flags/UV=] [=flag=].

- The [=BE=] [=flag=] SHALL be set if and only if the credential is a [=multi-device credential=].
This value MUST NOT change after a [=registration ceremony=] as defined in [[#sctn-credential-backup]].

- The [=BS=] [=flag=] SHALL be set if and only if the credential is a [=multi-device credential=] and is currently [=backed up=].

If the backup status of a credential is uncertain or the authenticator suspects a problem with the backed up credential,
the [=BS=] [=flag=] SHOULD NOT be set.

- For [=attestation signatures=], the authenticator MUST set the [=AT=] [=flag=] and include the <code>[=attestedCredentialData=]</code>.
For [=assertion signatures=], the [=AT=] [=flag=] MUST NOT be set and the <code>[=attestedCredentialData=]</code> MUST NOT be included.

Expand Down