- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Jun 2017 23:57:05 +0000
- To: public-webauthn@w3.org
re-opening since the alignment-with-credman work we did in PR #384 and subsequently has violated @bzbarsky's assertion in the orig post (OP) above that "Whatever work is done with settings objects and origins needs to be done before going async." credman's [Create a `Credential`](https://w3c.github.io/webappsec-credential-management/#algorithm-create) and [Request a `Credential`](https://w3c.github.io/webappsec-credential-management/#algorithm-request) algorithms "go async" (i.e., invoke [=in parallel=]) before calling into webauthn's [Create a new credential](https://w3c.github.io/webauthn/#createCredential) and [Use an existing credential to make an assertion](https://w3c.github.io/webauthn/#getAssertion) algorithms (respectively) Do we indeed have an issue here? /cc @bzbarsky @domenic @jyasskin @mikewest -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/254#issuecomment-309924219 using your GitHub account
Received on Tuesday, 20 June 2017 23:57:12 UTC