読み込み中...
読み込み中...
W3C WebAuthn Level 2 Recommendationに基づき、RP-scoped credential、3つの役割、registration/authentication API、RP server verificationをexact5で確認できます。
最終更新日 ・ by yuzlrin
| 項目 | 内容 |
|---|---|
| Credential | RP-scoped public-key credential — A public-key credential source is scoped to a Relying Party identifier; it is not a portable password or a universal account identifier. (§4) |
| Roles | Relying Party / Client / Authenticator — The Relying Party requests registration or authentication, the client mediates the ceremony, and the authenticator creates or uses the credential source. (§4) |
| Registration API | navigator.credentials.create({ publicKey }) — The client-side entry point requests creation of a public-key credential; successful resolution still requires the Relying Party's registration verification in §7.1. (§5.1.3) |
| Authentication API | navigator.credentials.get({ publicKey }) — The client-side entry point requests a public-key credential assertion; successful resolution still requires the Relying Party's assertion verification in §7.2. (§5.1.4) |
| Server verification | RP server verifies challenge / origin / RP ID / signature and applicable ceremony checks — Registration §7.1 and assertion verification §7.2 require server-side checks appropriate to the ceremony; API resolution alone is insufficient. (§7.1 / §7.2) |