Skip to content

Commit fda7a37

Browse files
committed
add missing step to ROR
1 parent 2775f50 commit fda7a37

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

  • content/en/docs/advanced/related-origins

content/en/docs/advanced/related-origins/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -201,8 +201,10 @@ This flow assumes the [autofill UI](/docs/reference/terms/#autofill-ui) for pass
201201
3. If the the user enters a username and continues:
202202
- abort the conditional WebAuthn request
203203
- send a request to your backend to retrieve the RP ID for the username
204-
4. Fetch fresh WebAuthn parameters from the backend
205-
5. Call WebAuthn with the fresh parameters and the correct RP ID
204+
4. Redirect the user to the origin matching the RP ID (typically using a federation protocol)
205+
5. Fetch fresh WebAuthn parameters from the backend
206+
6. Call WebAuthn with the fresh parameters and the correct RP ID
207+
7. Redirect the user back to the original origin with the necessary artifacts (typically a federated assertion or token)
206208

207209
#### Example
208210

@@ -213,7 +215,7 @@ In this example, passkeys have previously been rolled out to the following users
213215

214216
A user with a passkey for `shopping.com` navigates to `https://shopping.com`, clicks into the username field, selects their passkey, performs user verification, and is then signed in!
215217

216-
A user with a passkey for `shopping.co.uk` has traveled to the US and navigates to `https://shopping.co.uk`. Based on location data, the user is redirected to `https://shopping.com`. They click into the username field and do not see any passkey available. They then type their username and click continue. A backend lookup occurs, and WebAuthn is now invoked with an RP ID of `shopping.co.uk` and the user selects their passkey, performs user verification, and is signed in!
218+
A user with a passkey for `shopping.co.uk` has traveled to the US and navigates to `https://shopping.co.uk`. Based on location data, the user is redirected to `https://shopping.com`. They click into the username field and do not see any passkey available. They then type their username and click continue. A backend lookup occurs, the user is redirected to `https://shopping.co.uk`, WebAuthn is now invoked with an RP ID of `shopping.co.uk`, the user selects their passkey, performs user verification, and is redirected back to `https://shopping.com`!
217219

218220
## Additional Information
219221

0 commit comments

Comments
 (0)