Skip to content

Commit 42ab092

Browse files
authored
Merge pull request #212
docs: Update fido2-auth-tokens.md
2 parents a5fbe56 + a037f36 commit 42ab092

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/users-manual/application-fido2/fido2-auth-tokens.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ In the SDK, an AuthToken is retrieved by calling one of the `Verify` methods, su
9797
* Send a command to the YubiKey containing the encrypted "PinHash", permissions, and other info
9898
* If the PIN was correct, the YubiKey verifies the "PinHash"
9999
* The YubiKey returns a PinUvAuthToken (with permissions attached), which is the AuthToken to use
100-
* PIN with permissions
100+
* UV with permissions
101101
* The caller supplies the permissions
102102
* Send a command to the YubiKey containing permissions, and other info
103103
* Upon receiving the command, the YubiKey will wait for the user to verify the fingerprint
@@ -157,7 +157,7 @@ An AuthToken's permissions can also expire. There are a number of ways to expire
157157
most common is when the YubiKey, upon receiving an AuthParam for one command, will
158158
"expire" an AuthToken, and it cannot be used again (in the FIDO2 terminology, "expire" is
159159
an active verb, it is something the YubiKey does to the PinToken). To perform another
160-
command requires the client retrieve a new AuthToken. In still other cases an AuthToken
160+
command requires the client to retrieve a new AuthToken. In still other cases an AuthToken
161161
can be "partially expired", where it can be reused for some commands, but not for others.
162162

163163
Note that "expire" will usually have nothing to do with time. That is, a YubiKey will
@@ -220,7 +220,7 @@ commands or several calls to the same command.
220220

221221
On a FIDO2 version 2.1 YubiKey, the PinToken can only be used to perform MakeCredential
222222
and GetAssertion. Furthermore, it can be expired, and in fact, it can be used to build an
223-
AuthParam that will authenticate only call to one command.
223+
AuthParam that will authenticate a call to only one command.
224224

225225
### PinUvAuthToken
226226

@@ -299,7 +299,7 @@ you will want to perform Bio Enrollment, get an AuthToken with that permission.
299299
know you will want to get an assertion and write data to the [large blob](large-blobs.md),
300300
get an AuthToken with those two permissions.
301301

302-
To get an AuthToken with permissions, call one of the `VerifyPin` or VerifyUv` methods.
302+
To get an AuthToken with permissions, call one of the `VerifyPin` or `VerifyUv` methods.
303303
For example
304304

305305
```csharp

0 commit comments

Comments
 (0)