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.

Sign up for GitHub

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

Jump to bottom

Define RP processing of be and bs flags during .create() and .get() #1907

Merged
merged 6 commits into from
Aug 9, 2023
Merged

Define RP processing of be and bs flags during .create() and .get() #1907

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
615e8e6
Assert that be:0+bs:1 is bad during create()
MasterKale Jun 14, 2023
72ef9bb
Assert be:1->be:0 or be:0+bs:1 are bad from get()
MasterKale Jun 14, 2023
d8b42fe
Require `be` not to change after .get()
MasterKale Jun 14, 2023
8a04cf7
Make consistent the check for be:0,bs:1 during reg
MasterKale Jun 28, 2023
3e0395f
Enforce rejection of be:0,bs:1 during auth
MasterKale Jun 28, 2023
4514f5f
Remove redundant step
MasterKale Jul 12, 2023
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
15 changes: 13 additions & 2 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5292,6 +5292,8 @@ In order to perform a [=registration ceremony=], the [=[RP]=] MUST proceed as fo
1. If the [=[RP]=] requires [=user verification=] for this registration,
verify that the [=authData/flags/UV=] bit of the <code>[=flags=]</code> in |authData| is set.

1. If the [=authData/flags/BE=] bit of the <code>[=flags=]</code> in |authData| is not set, verify that the [=authData/flags/BS=] bit is not set.

1. If the [=[RP]=] uses the credential's [=backup eligibility=] to inform its user experience flows and/or policies, evaluate the
[=authData/flags/BE=] bit of the <code>[=flags=]</code> in |authData|.

Expand Down Expand Up @@ -5517,12 +5519,21 @@ a numbered step. If outdented, it (today) is rendered as a bullet in the midst o
verify that the [=authData/flags/UV=] bit of the <code>[=flags=]</code> in |authData| is set.
Otherwise, ignore the value of the [=authData/flags/UV=] [=flag=].

1. If the [=authData/flags/BE=] bit of the <code>[=flags=]</code> in |authData| is not set, verify that the [=authData/flags/BS=] bit is not set.

1. If the credential [=backup state=] is used as part of [=[RP]=] business logic or policy,
let |currentBe| and |currentBs| be the values of the [=authData/flags/BE=] and [=authData/flags/BS=] bits, respectively,
of the <code>[=flags=]</code> in |authData|.
Compare |currentBe| and |currentBs| with
<code>|credentialRecord|.[$credential record/backupEligible$]</code> and <code>|credentialRecord|.[$credential record/backupState$]</code>
and apply [=[RP]=] policy, if any.
<code>|credentialRecord|.[$credential record/backupEligible$]</code> and <code>|credentialRecord|.[$credential record/backupState$]</code>:

1. If <code>|credentialRecord|.[$credential record/backupEligible$]</code> is set, verify that |currentBe| is set.

1. If <code>|credentialRecord|.[$credential record/backupEligible$]</code> is not set, verify that |currentBe| is not set.

1. If <code>|credentialRecord|.[$credential record/backupEligible$]</code> is not set, verify that |currentBs| is not set.
MasterKale marked this conversation as resolved.
Show resolved Hide resolved

1. Apply [=[RP]=] policy, if any.
emlun marked this conversation as resolved.
Show resolved Hide resolved

Note: See [[#sctn-credential-backup]] for examples of how a [=[RP]=] might process the [=authData/flags/BS=] [=flag=] values.

Expand Down