From aa2d547eb27e75920a980faa722f8ad3076224d6 Mon Sep 17 00:00:00 2001
From: Livio Spring <livio.a@gmail.com>
Date: Sat, 19 Aug 2023 08:26:51 +0200
Subject: [PATCH] docs: update passkey usage in session api (#6386)

Co-authored-by: Stefan Benz <46600784+stebenz@users.noreply.github.com>
---
 docs/docs/guides/integrate/login-ui/passkey.mdx | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/docs/docs/guides/integrate/login-ui/passkey.mdx b/docs/docs/guides/integrate/login-ui/passkey.mdx
index bec0a2d60..247d8229b 100644
--- a/docs/docs/guides/integrate/login-ui/passkey.mdx
+++ b/docs/docs/guides/integrate/login-ui/passkey.mdx
@@ -212,7 +212,7 @@ Next step is to authenticate the user with the new registered passkey.
 ### Create Session
 
 First step is to ask the user for his username and create a new session with the ZITADEL API.
-When creating the new session make sure to include the challenge for passkey.
+When creating the new session make sure to include the challenge for passkey, resp. webAuthN with a required user verification and the domain of your login UI.
 The response will include the public key credential request options for the passkey in the challenges.
 
 More detailed information about the API: [Create Session Documentation](/apis/resources/session_service/session-service-create-session)
@@ -231,9 +231,12 @@ curl --request POST \
     }
   },
   "metadata": {},
-  "challenges": [
-    "CHALLENGE_KIND_PASSKEY"
-  ]
+  "challenges": {
+    "webAuthN": {
+      "domain": "example.domain.com",
+      "userVerificationRequirement": "USER_VERIFICATION_REQUIREMENT_REQUIRED"
+    }
+  }
 }'
 ```
 
@@ -248,7 +251,7 @@ Example Response:
   "sessionId": "d654e6ba-70a3-48ef-a95d-37c8d8a7901a",
   "sessionToken": "string",
   "challenges": {
-    "passkey": {
+    "webAuthN": {
       "publicKeyCredentialRequestOptions": {
         "publicKey": {
           "allowCredentials": [
@@ -274,7 +277,7 @@ After starting the passkey authentication on the side of ZITADEL you have to cha
 To do this you need to call the browser API to get the credentials.
 Make sure to send the public key credential request options you got from ZITADEL.
 
-```bash
+```javascript
 const credential = await navigator.credentials.get({
     publicKey: publicKeyCredentialRequestOptions
 });
@@ -300,7 +303,7 @@ curl --request PATCH \
   --data '{
   "sessionToken": "yMDi6uVPJAcphbbz0LaxC07ihWkNTe7m0Xqch8SzfM5Cz3HSIQIDZ65x1f5Qal0jxz0MEyo-_zYcUg",
   "checks": {
-    "passkey": {
+    "webAuthN": {
       "credentialAssertionData": {}
     }
   }