- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Oct 2020 15:29:55 +0000
- To: public-webauthn@w3.org
equalsJeffH has just created a new issue for https://github.com/w3c/webauthn: == double check whether the Secure Payment Confirmation effort has implications on the WebAuthn spec == https://chromestatus.com/feature/5702310124584960 it is possible, but am not sure how likely, that we might want to put a Note or other mention of different RP hostname mapping/handling in the layer underneath the webauthn api. this is because the webauthn spec is the specificatoin of the protocol between the RP and the authenticator (N.B. CTAP is a spec of just one manifestation of the comms btwn the client platform and the authnr, and it conveys the signed object back from the authnr to the client platform as an opaque blob -- webauthn is the definitive spec of its contents, and thus the "protocol spec" for authnr <----> RP). Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1492 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 October 2020 15:29:57 UTC