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

GetAssertionOptionUvTrueTest - pinUvAuthToken can't be used again for GetAssertionPositiveTest. #111

Open
nuno0529 opened this issue Feb 19, 2021 · 1 comment
Assignees

Comments

@nuno0529
Copy link

In latest ctap2.1 spec, step 6.1.2.14 If the "up" option is set to true:
The last step4. will Call clearUserPresentFlag(), clearUserVerifiedFlag(), and clearPinUvAuthTokenPermissionsExceptLbw().
So the result of following GetAssertionPositiveTest should be always failed due to below line use an old authToken directly.

options_builder.SetDefaultPinUvAuthParam(
      command_state->GetCurrentAuthToken());

Seems following test items in will have the same problem.

  • GetAssertionPinAuthTest
  • GetAssertionPinAuthMissingParameterTest
@kaczmarczyck kaczmarczyck self-assigned this Feb 22, 2021
@kaczmarczyck
Copy link
Collaborator

Thanks for flagging this for CTAP2.1!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants