Hi Group,
I have been looking and experimenting around WebAuthN Conditional Create, particularly around requests for related origins.
Scenario:
2. User uses password manager to fill username and password on
a.example.com3. Browser redirects to
b.example.com and tries to create a conditional passkey
a).
navigator.credentials.create({ mediation: 'conditional', rpID:
a.example.com b)
. navigator.credentials.create({ mediation: 'conditional', rpID:
b.example.com
Observation:
a) and b) both result in a NotAllow error from the user agent (Chrome)
I might have missed it from the
spec but I did not find any particular discussions on related origins for conditional create. I do see a one-liner on the
explainer "
The origin of the document where the authentication ceremony was mediated and the origin where navigator.credentials.create must be the same" but wasn't sure if that's a not allowed even for related origin scenario.
Question:
1. Is related origins not allowed for WebAuthN conditional create at all?
2. If this is not an allowed scenario, would we consider to support this scenario in the future? We allowed Conditional UI (get) for related origin requests, I think this is similar scenario just with create.
Thanks,
Jack