Skip to content
GitLab
Explore
Projects
Groups
Topics
Snippets
Projects
Groups
Topics
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
fusiondirectory
WebAuthn
Commits
6f25c5ad
Commit
6f25c5ad
authored
4 years ago
by
Lukas Buchs
Browse files
Options
Download
Patches
Plain Diff
No commit message
No commit message
parent
d52116a0
master
v2.0.0-beta
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.0
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+10
-7
README.md
with
10 additions
and
7 deletions
+10
-7
README.md
+
10
−
7
View file @
6f25c5ad
...
...
@@ -54,17 +54,18 @@ A Client-side-resident Public Key Credential Source, or Resident Credential for
is a public key credential source whose credential private key is stored in the authenticator,
client or client device. Such client-side storage requires a resident credential capable authenticator.
This is only supported by FIDO2 hardware, not by older U2F hardware.
On the browser side, at the moment only Microsoft Edge 18 seems to be supporting it.
### How does it work?
With normal
**server-side key**
process, the user enters its username (and maybe password),
then the server replys with a list of all public key credential identifier, which had been registered by the user.
Then, the authenticator takes the first of the provided credential identifier, which has been issued by himself,
and responses with a signature which can be validated with the public key provided on registration.
With
**client-side key**
process, the user don't have to provide
it's
username or password
, he can actually just press a 'login' button!
The
n, the
server don't send any identifier; rather, the authenticator is looking up in it's own memory,
With
**client-side key**
process, the user don't have to provide
an
username or password
.
The server don't send any identifier; rather, the authenticator is looking up in it's own memory,
if there is a key saved for this relying party. If yes, he's responding the same way like he's doing if you provide a
list of identifier, there is no difference in checking the registration.
Resident Credential is supported by Windows 10 (Firefox, Chromium). Browser on old OS like Windows 7
do a fallback to FIDO U2F, which doesn't support resident credential.
### How can I use it with this library?
#### on registration
...
...
@@ -86,11 +87,13 @@ When calling `WebAuthn\WebAuthn->getGetArgs`, don't provide any `$credentialIds`
*
[
FIDO Alliance
](
https://fidoalliance.org
)
## FIDO2 Hardware
*
[
Yubico
](
https://www.yubico.com
/products/yubikey-hardware/compare-yubikeys/
)
*
[
Yubico
](
https://www.yubico.com
)
*
[
Solo
](
https://solokeys.com
)
Open Source!
*
[
Feitan
](
https://www.ftsafe.com/Products/FIDO2
)
*
[
eWBM
](
http://www.e-wbm.com/fido_usb.jsp
)
*
[
Nitrokey
](
https://www.nitrokey.com/
)
*
[
Feitan
](
https://fido.ftsafe.com/
)
*
[
TrustKey
](
https://www.trustkeysolutions.com
)
*
[
Google Titan
](
https://cloud.google.com/titan-security-key
)
*
[
Egis
](
https://www.egistec.com/u2f-solution/
)
*
[
OneSpan
](
https://www.vasco.com/products/two-factor-authenticators/hardware/one-button/digipass-secureclick.html
)
*
[
Hypersecu
](
https://hypersecu.com/products/hyperfido
)
\ No newline at end of file
*
[
Hypersecu
](
https://hypersecu.com/tmp/products/hyperfido
)
*
[
Kensington VeriMark™
](
https://www.kensington.com/
)
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment
Menu
Explore
Projects
Groups
Topics
Snippets