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

Refine User Verification description #1162

Closed
Kieun opened this issue Feb 22, 2019 · 3 comments · Fixed by #1238
Closed

Refine User Verification description #1162

Kieun opened this issue Feb 22, 2019 · 3 comments · Fixed by #1238

Comments

@Kieun
Copy link
Member

Kieun commented Feb 22, 2019

The description of User Verification includes following sentence.

The intent is to be able to distinguish individual users.

In fact, If we enroll multiple fingerprints of family members to the authenticator (device), the authenticator never identify the each users. But, this sentence may mislead to readers that the authenticator can distinguish or identify the users.

It is more like the process that checks the user's authority to register the credential or authenticate with the credential.

@nadalin nadalin added this to the L2-WD-02 milestone Feb 27, 2019
@emlun
Copy link
Member

emlun commented Feb 27, 2019

It is true that authenticators might allow registering several people's fingerprints to the same account, for example, but I'd argue it's still true that the intent of UV is to distinguish individual users. Also, multiple people could very well share the same "user" account at an RP anyway. I don't think we really need to change anything here.

@emlun
Copy link
Member

emlun commented Feb 27, 2019

On second thought, maybe we should acually define the term "user". Then that definition could point out that a user could be one or more physical persons.

@leshi
Copy link
Contributor

leshi commented Mar 6, 2019

I suggest saying "legitimate device owner" or "device owner"

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

Successfully merging a pull request may close this issue.

4 participants