Skip to content

Commit a07e598

Browse files
authored
Merge pull request #463 from passkeydeveloper/mm/ror-refine-federation-guidance
Emphasize the importance of federation over ROR first
2 parents 5ed27d0 + 4fc642d commit a07e598

2 files changed

Lines changed: 8 additions & 3 deletions

File tree

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,13 @@ layouts: docs
88

99
## Use Cases
1010

11-
The two use cases for Related Origin Requests (ROR) are deployments which use different country code top-level domains (ccTLD) across the world, and deployments where different branding is used for different services.
11+
Where suppoted, Related Origin Requests (ROR) can help Relying Parties offer users the ability to use a single origin-bound passkey across the following deployment patterns:
1212

13-
To address these use cases, it is recommended to leverage industry-standard federation protocols such as [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html). This approach facilitates a centralized login experience, by using a dedicated login page (e.g., login.example.com) that serves as the authentication point for all origins and services.
13+
1. Deployments that use different country code top-level domains (ccTLD) across the world
14+
2. Deployments where a single company's different services are served from different domains
1415

15-
**ROR is designed to be used when federation is _not_ possible.**
16+
> [!WARNING]
17+
> **ROR is designed to be used when federation is _not_ possible!** It is **recommended** that Relying Parties first consider leveraging industry-standard federation protocols such as [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html). Federation achieves a centralized login experience by using a dedicated login page (e.g., login.example.com) that serves as the authentication point for all origins and services.
1618
1719
> [!NOTE]
1820
> ROR is a WebAuthn feature for the web. App platforms have existing mechanisms for mapping native apps to one or more web origins: [Digital Asset Links](https://developers.google.com/identity/credential-sharing/set-up) for Android and [Associated Domains](https://developer.apple.com/documentation/xcode/supporting-associated-domains) on Apple platforms.

hugo_stats.json

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,7 @@
7878
"blockquote-alert",
7979
"blockquote-alert-heading",
8080
"blockquote-alert-note",
81+
"blockquote-alert-warning",
8182
"border",
8283
"border-0",
8384
"border-top",
@@ -172,6 +173,7 @@
172173
"fa-sort",
173174
"fa-sun",
174175
"fa-threads",
176+
"fa-triangle-exclamation",
175177
"fa-user-shield",
176178
"fa-wand-magic-sparkles",
177179
"fa-whatsapp",
@@ -454,6 +456,7 @@
454456
"fas-share-nodes",
455457
"fas-sort",
456458
"fas-sun",
459+
"fas-triangle-exclamation",
457460
"fas-user-shield",
458461
"fas-wand-magic-sparkles",
459462
"fido2webauthn-tools",

0 commit comments

Comments
 (0)