Menu

WebAuthn RP IDs Turn a Subdomain Decision into an Authentication Boundary
📰

WebAuthn RP IDs Turn a Subdomain Decision into an Authentication Boundary

DEV Community: security·kozhevniko·8 days ago
#be9FxhDM
Reading 0:00
15s threshold

WebAuthn RP IDs Turn a Subdomain Decision into an Authentication Boundary

WebAuthn registrations are bound to a relying party identifier, or RP ID. The browser and authenticator use that identifier to decide whether a credential belongs to a site. The default RP ID is the caller's effective domain, according to the Web Authentication specification. A team can choose a broader registrable-domain suffix, which is convenient for a product spread across several subdomains. That convenience also widens the set of origins that can request an authentication ceremony with the same credential family.

The RP ID is not a password and does not leave the authenticator's private key exposed. The important boundary is the relationship between the RP ID, the browser's origin checks, and the server's own verification. The current WebAuthn specification notes that origin validation is an additional layer of protection when an authenticator fails to enforce credential scope.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.