<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Advanced on passkeys.dev</title><link>https://d946ac66.passkeys-dev.pages.dev/docs/advanced/</link><description>Recent content in Advanced on passkeys.dev</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://d946ac66.passkeys-dev.pages.dev/docs/advanced/index.xml" rel="self" type="application/rss+xml"/><item><title>Client Hints</title><link>https://d946ac66.passkeys-dev.pages.dev/docs/advanced/client-hints/</link><pubDate>Wed, 24 Sep 2025 05:07:38 +0000</pubDate><guid>https://d946ac66.passkeys-dev.pages.dev/docs/advanced/client-hints/</guid><description>&lt;h2 id="overview" class="heading "&gt;Overview&lt;a href="#overview" aria-labelledby="overview"&gt;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 576 512" overflow="visible"&gt;&lt;use href="#fas-link"&gt;&lt;/use&gt;&lt;/svg&gt;&amp;nbsp;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;When creating a passkey, WebAuthn Clients display a credential manager selection screen asking users to choose where to store their new passkey. The selector typically defaults to local credential managers because they offer immediate availability and support for synced passkeys, the default credential type in unmanaged, consumer contexts.&lt;/p&gt;
&lt;p&gt;During a sign in flow, the WebAuthn Client will do its best to help the user select a passkey which is immediately available, and fall back to an external authenticator selection screen. This typically shows an option for 
 &lt;a href="https://d946ac66.passkeys-dev.pages.dev/docs/reference/terms#cross-device-authentication-cda"&gt;FIDO Cross-Device Authentication&lt;/a&gt;
 and security keys. In environments where only security keys are allowed, having additional options such as displaying a QR code for cross-device authentication flows can confuse users and lead to unnecessary support costs.&lt;/p&gt;</description></item><item><title>Related Origin Requests</title><link>https://d946ac66.passkeys-dev.pages.dev/docs/advanced/related-origins/</link><pubDate>Thu, 22 Aug 2024 15:20:51 +0000</pubDate><guid>https://d946ac66.passkeys-dev.pages.dev/docs/advanced/related-origins/</guid><description>&lt;h2 id="use-cases" class="heading "&gt;Use Cases&lt;a href="#use-cases" aria-labelledby="use-cases"&gt;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 576 512" overflow="visible"&gt;&lt;use href="#fas-link"&gt;&lt;/use&gt;&lt;/svg&gt;&amp;nbsp;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Deployments that use different country code top-level domains (ccTLD) across the world&lt;/li&gt;
&lt;li&gt;Deployments where a single company&amp;rsquo;s different services are served from different domains&lt;/li&gt;
&lt;/ol&gt;



 
 

 &lt;blockquote class="blockquote-alert blockquote-alert-warning"&gt;
 &lt;p class="blockquote-alert-heading"&gt;
 
 






 
 
 
 &lt;svg class="svg-inline--fa fas fa-triangle-exclamation fa-fw" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-triangle-exclamation"&gt;&lt;/use&gt;&lt;/svg&gt;&amp;nbsp;
 Warning
 
 &lt;/p&gt;</description></item></channel></rss>