Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs-staging.auth0-mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The MyAccountAuthMethodsView component can render the Auth0 passkey enrollment flow. The passkey enrollment flow renders an educational screen, a WebAuthn registration handshake with the platform authenticator, and the enrolled-factor entry in the authenticator list. Unlike other factors, passkeys require application-side platform entitlements that the Universal Components for iOS SDK cannot configure.
Passkey enrollment screen showing educational content and Create a Passkey button

​
Prerequisites

To enable passkey support in the Universal Components for iOS SDK:

​
Platform setup

​
Add the associated domain in Xcode

After registering your Apple Team ID and Bundle ID in your Auth0 application’s Device Settings, Auth0 serves the AASA file from your custom domain. Add your Auth0 custom domain to the application:
  1. Open Xcode.
  2. Select your target’s Signing & Capabilities.
  3. Add a Capability and select Associated Domains.
  4. Enter your Auth0 custom domain: 
    webcredentials:YOUR_AUTH0_DOMAIN
  5. Confirm that Signing & Capabilities → Team matches the Apple Team ID you registered in your Auth0 application’s Device Settings, and that the target’s Bundle Identifier matches the registered Bundle ID exactly. iOS performs a case-sensitive byte-for-byte match — for example, com.example.OAuth2 is not the same as com.example.oauth2.
During development, Apple’s CDN can cache stale AASA files for hours after you change Device Settings.To fetch the AASA directly from your tenant during development, append ?mode=developer to the entitlement (for example, webcredentials:YOUR_AUTH0_DOMAIN?mode=developer) and enable Settings → Developer → Associated Domains Development on the device.Test on a physical device, the iOS Simulator does not reliably honor associated-domain configuration. Remove the ?mode=developer suffix before shipping a release build.

​
SDK limitations

  • Passkeys can only be enrolled from inside the MyAccountAuthMethodsView component. There is no public SwiftUI API to trigger a standalone passkey enrollment from elsewhere in your application. Post-login “save a passkey” upsell prompts are not supported. You can track ui-components-ios for updates.
  • Removing a passkey in the component does not purge the OS credential store. The enrolled passkey detaches from the Auth0 account, but the private credential remains in iCloud Keychain until the user removes it from the OS-level credential manager.
  • Attestation conveyance is not surfaced. The SDK does not let you select the attestation policy (none / indirect / direct) or enumerate authenticator transports. It uses the Auth0 tenant’s configured WebAuthn policy.

​
Learn more

Auth Methods Management

Review the MyAccountAuthMethodsView component reference and the full list of supported factors.

Build a Self-Service Account Security Interface

Initialize the SDK and wire the token provider to your Auth0 tenant.