RPID for Passkeys by avanscoy · Pull Request #604 · auth0/docs-v2

avanscoy · 2026-02-12T22:07:46Z

First updates for Relying Party ID for Passkeys, fixed Native Mobile pages missing in Nav

Description

Adding RPID to main docs as this feature is rolling out limited EA.

References

Testing

Checklist

I've read and followed CONTRIBUTING.md.
I've tested the site build for this change locally.
I've made appropriate docs updates for any code or config changes.
I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

…pages missing in Nav

github-actions · 2026-02-12T22:08:15Z

Summary

Status	Count
🔍 Total	108
✅ Successful	25
⏳ Timeouts	0
🔀 Redirected	4
👻 Excluded	78
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	0

Errors per input

Errors in main/docs/authenticate/database-connections/passkeys.mdx

[ERROR] https://fidoalliance.org/passkeys/#faq | Cannot find fragment: Fragment not found in document. Check if fragment exists or page structure

Redirects per input

Redirects in main/docs/secure/multi-factor-authentication/fido-authentication-with-webauthn/configure-webauthn-device-biometrics-for-mfa.mdx

[200] https://a0.to/webauthme-auth0-docs | Redirect: Followed 2 redirects resolving to the final status of: OK. Redirects: https://a0.to/webauthme-auth0-docs --> https://webauthn.me/?utm_source=auth0_docs&utm_medium=organic_dist&utm_campaign=auth0-docs --> https://www.webauthn.me/?utm_source=auth0_docs&utm_medium=organic_dist&utm_campaign=auth0-docs
[200] https://webauthn.me/browser-support | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://webauthn.me/browser-support --> https://www.webauthn.me/browser-support
[200] https://webauthn.me/introduction | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://webauthn.me/introduction --> https://www.webauthn.me/introduction

Redirects in main/docs/secure/multi-factor-authentication/fido-authentication-with-webauthn/configure-webauthn-security-keys-for-mfa.mdx

[200] https://webauthn.me/browser-support | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://webauthn.me/browser-support --> https://www.webauthn.me/browser-support
Full Github Actions output

nick-gagliardi · 2026-02-18T15:52:18Z

main/docs/customize/custom-domains.mdx

 * It's harder to phish your domain if you have a vanity URL because the phisher must create a vanity URL to mimic yours. For example, with a custom domain, you can use your own certificate to get an Extended Validation, making phishing harder.
+* [Passkeys](/docs/authenticate/database-connections/passkeys), a phishing-resistant alternative to traditional authentication factors, are bound to your custom domain by the relying party ID attribute `rpId`. Before you configure your custom domain, we recommend you use the parent or origin (e.g. `yourDomain.com`) rather than a subdomain (`login.yourDomain.com`). If your custom domain in Auth0 is set to the origin, end users can use a single passkey to authenticate across native or mobile web applications. To learn more, read [Configure Passkey Policy](/docs/authenticate/database-connections/passkeys/configure-passkey-policy#configure-relying-party-id-rpid).
+
+<Callout icon="file-lines" color="#0EA5E9" iconType="regular">


empty callout

nick-gagliardi · 2026-02-18T15:53:12Z

.../docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications.mdx

+     "access_token": "{BASE64_TOKEN}",
+     "refresh_token": "{BASE64_TOKEN}",
+     "id_token": "{BASE64_TOKEN}",
+     "token_type": "Bearer:",


Suggested change

"token_type": "Bearer:",

"token_type": "Bearer",

nick-gagliardi · 2026-02-18T15:54:02Z

main/docs/authenticate/database-connections/passkeys.mdx

+Passkeys are a phishing-resistant alternative to traditional authentication factors (such as identifier/password) that offer an easier and more secure login experience to users. Passkeys are modeled from FIDO® W3C Web Authentication (WebAuthn) and Client to Authenticator Protocol (CTAP) [specifications](https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-errata-20220621.html#intro).

-Passkeys reduce the friction experienced with single-device authentication methods by allowing credentials to sync across devices. Cross-device authentication eliminates the need for users to re-enroll on each of their devices. It also supports a more reliable recovery method as the stored credentials can survive the loss of an originating device. To learn more about passkeys, review the FIDO® Alliance [Passkey FAQs](https://fidoalliance.org/passkeys/#faq).
+Passkeys reduce the friction experienced with single-device authentication methods by allowing credentials to sync across devices and map to associated domains. WebAuthn binds credentials like passkeys to a specific domain identified by the [Relying Party ID attribute](https://www.w3.org/TR/webauthn-2/#relying-party-identifier) to bind the passkey to the domain from which is what created and can authenticate. For example, if your web application is served at `login.example.com` and your native application served at `app.example.com`, you can configure the <Tooltip tip="Relying Party: Entity (such as a service or application) that depends on a third-party identity provider to authenticate a user." cta="View Glossary" href="/docs/glossary?term=Relying+Party">Relying Party</Tooltip> ID to `example.com`. End users are able to authenticate to any `example.com` domain with a single passkey.


"to bind the passkey to the domain from which is what created and can authenticate."

double-check this

nick-gagliardi · 2026-02-18T15:54:30Z

main/docs/authenticate/database-connections/passkeys.mdx

+Auth0 supports passkeys as an authentication method for [database connections](/docs/authenticate/database-connections) and offers three methods of implementation:
+* Universal Login passkeys for web-based applications
+* [Embedded Login for web-based and native applications](/docs/authenticate/passwordless/implement-login/embedded-login)
+* [Native passkeys for Android and iOS applications](docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications)


Suggested change

* [Native passkeys for Android and iOS applications](docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications)

* [Native passkeys for Android and iOS applications](/docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications)

nick-gagliardi · 2026-02-18T15:56:00Z

main/docs/authenticate/database-connections/passkeys/native-passkeys-api.mdx

+    },
  }
-}
+},


Suggested change

},

}

nick-gagliardi · 2026-02-18T15:57:29Z

.../docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications.mdx

 Native passkeys require the use of a <Tooltip tip="Custom Domain: Third-party domain with a specialized, or vanity, name." cta="View Glossary" href="/docs/glossary?term=custom+domain">custom domain</Tooltip>. Before proceeding, ensure you have configured a custom domain for your tenant. To learn more, review [Custom Domains](/docs/customize/custom-domains).

+<Callout icon="file-lines" color="#0EA5E9" iconType="regular">
+To enable passkey sharing across application types with relying party ID (RPID), make sure you native application's metadata matches the custom domain's origin. For example, if your native application is served at `app.example.com`, your custom domain origin should be `example.com`.


Suggested change

To enable passkey sharing across application types with relying party ID (RPID), make sure you native application's metadata matches the custom domain's origin. For example, if your native application is served at `app.example.com`, your custom domain origin should be `example.com`.

To enable passkey sharing across application types with relying party ID (RPID), make sure your native application's metadata matches the custom domain's origin. For example, if your native application is served at `app.example.com`, your custom domain origin should be `example.com`.

First updates for Relying Party ID for Passkeys, fixed Native Mobile …

9c46cb2

…pages missing in Nav

avanscoy requested review from a team as code owners February 12, 2026 22:07

avanscoy added main-docs Changes related to auth0's main docs (https://auth0.com/docs) DO NOT MERGE Only the PR author should merge, even if approved. labels Feb 12, 2026

mintlify bot deployed to staging - main February 12, 2026 22:16 View deployment

Native mobile and Native API

c1a9e95

mintlify bot deployed to staging - main February 13, 2026 18:38 View deployment

Custom Domains. Pending MCD and Embedded

703f930

mintlify bot deployed to staging - main February 13, 2026 19:07 View deployment

Params punctuation

33f77a3

mintlify bot deployed to staging - main February 13, 2026 19:37 View deployment

Updates based on Dashboard changes

9e115e6

mintlify bot deployed to staging - main February 18, 2026 00:55 View deployment

avanscoy removed the DO NOT MERGE Only the PR author should merge, even if approved. label Feb 18, 2026

nick-gagliardi reviewed Feb 18, 2026

View reviewed changes

Addressed comments

0b8352f

mintlify bot deployed to staging - main February 18, 2026 17:21 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

RPID for Passkeys#604

RPID for Passkeys#604
avanscoy wants to merge 6 commits intomainfrom
feat/docs-5288-rpid-passkeys

avanscoy commented Feb 12, 2026

Uh oh!

github-actions bot commented Feb 12, 2026 •

edited

Loading

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

nick-gagliardi Feb 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	* [Native passkeys for Android and iOS applications](docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications)
	* [Native passkeys for Android and iOS applications](/docs/authenticate/database-connections/passkeys/native-passkeys-for-mobile-applications)

	To enable passkey sharing across application types with relying party ID (RPID), make sure you native application's metadata matches the custom domain's origin. For example, if your native application is served at `app.example.com`, your custom domain origin should be `example.com`.
	To enable passkey sharing across application types with relying party ID (RPID), make sure your native application's metadata matches the custom domain's origin. For example, if your native application is served at `app.example.com`, your custom domain origin should be `example.com`.

Comments

Conversation

avanscoy commented Feb 12, 2026

Description

References

Testing

Checklist

Uh oh!

github-actions bot commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Errors per input

Errors in main/docs/authenticate/database-connections/passkeys.mdx

Redirects per input

Redirects in main/docs/secure/multi-factor-authentication/fido-authentication-with-webauthn/configure-webauthn-device-biometrics-for-mfa.mdx

Redirects in main/docs/secure/multi-factor-authentication/fido-authentication-with-webauthn/configure-webauthn-security-keys-for-mfa.mdx

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

nick-gagliardi Feb 18, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions bot commented Feb 12, 2026 •

edited

Loading