Tenant boundaries in WebAuthn start with the RP ID
WebAuthn gives an application a strong way to bind a credential to an origin and a relying party. It does not decide which tenant owns an account or whether a user handle is safe to reuse. Those are application decisions made around the ceremony. Multi-tenant systems need to treat the relying party identifier and the user handle as security-boundary data, not as convenient configuration defaults.
The Web Authentication specification defines the relying party identifier, or RP ID, as a valid domain string that identifies the relying party. A credential is scoped to that RP ID. The browser also supplies the caller's origin in the collected client data, and the relying party verifies that origin. A server that checks an assertion signature but ignores the RP ID or origin policy has checked only part of the ceremony.
Use a domain that belongs to the tenant boundary
The RP ID must be equal to or a registrable domain suffix of the caller's effective domain.…