Difference between revisions of "Web Authentication Level 2"

From MgmtWiki
Jump to: navigation, search
(Context)
(Context)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Full Title==
 
==Full Title==
[[Web Authentication Level 2]] enables the creation and use of strong, attested, scoped, public key cred by web applications for strongly authenticating users.
+
[[Web Authentication Level 2]]<ref name=balfanz>Dirk Balfanz + 19, ''Web Authentication: An API for accessing Public Key Credentials Level 2 W3C Working Draft, 2020-07-30'' https://www.w3.org/TR/webauthn-2/#iface-pkcredential</ref> enables the creation and use of strong, attested, scoped, public key cred by web applications for strongly authenticating users.
  
 
==Context==
 
==Context==
 
* This is designed for web applications, not native applications.
 
* This is designed for web applications, not native applications.
 
* The current draft of the evolving standard is available [https://www.w3.org/TR/webauthn-2/ here].
 
* The current draft of the evolving standard is available [https://www.w3.org/TR/webauthn-2/ here].
 +
===Glossary===
 +
* Authenticator protects public key credentials, and interact with user agents to implement the Web Authentication API. Implementing compliant authenticators is possible in software executing (a) on a general-purpose computing device, (b) on an on-device Secure Execution Environment, Trusted Platform Module (TPM), or a Secure Element (SE), or (c) off device. Authenticators being implemented on device are called platform authenticators. Authenticators being implemented off device (roaming authenticators) can be accessed over a transport method.
 +
 
==Normal Flow==
 
==Normal Flow==
#
+
Web Authentication API <ref name=balfanz /> Section 5
 +
*Registration
 +
# Challenge, user info, RP info
 +
# RP ID, client data hash
 +
# User verification, new key pair
 +
*Authentication
 +
# Challenge
 +
# RP ID, client data hash
 +
# User verification
  
 
==Referrences==
 
==Referrences==

Latest revision as of 20:56, 26 October 2020

Full Title

Web Authentication Level 2[1] enables the creation and use of strong, attested, scoped, public key cred by web applications for strongly authenticating users.

Context

  • This is designed for web applications, not native applications.
  • The current draft of the evolving standard is available here.

Glossary

  • Authenticator protects public key credentials, and interact with user agents to implement the Web Authentication API. Implementing compliant authenticators is possible in software executing (a) on a general-purpose computing device, (b) on an on-device Secure Execution Environment, Trusted Platform Module (TPM), or a Secure Element (SE), or (c) off device. Authenticators being implemented on device are called platform authenticators. Authenticators being implemented off device (roaming authenticators) can be accessed over a transport method.

Normal Flow

Web Authentication API [1] Section 5

  • Registration
  1. Challenge, user info, RP info
  2. RP ID, client data hash
  3. User verification, new key pair
  • Authentication
  1. Challenge
  2. RP ID, client data hash
  3. User verification

Referrences

  1. 1.0 1.1 Dirk Balfanz + 19, Web Authentication: An API for accessing Public Key Credentials Level 2 W3C Working Draft, 2020-07-30 https://www.w3.org/TR/webauthn-2/#iface-pkcredential