Re: [webauthn] Include an AuthenticatorTransport when creating a new credential.

For the second thing about prompting user when RP knows that it only created platform authenticator in first place is one of the gaps that we missed and boils down to not having attachment property in getAssertion. This becomes very relevant when user moves to a brand new machine and tries to login or the same machine gets reset. 

We have to decide how much important are these issues and whether spec needs to be changed at this time of the game. I think we have two options, either break the spec and add attachment property in getAssertion similar to MakeCredential OR go via an extension route. 

I would not put "internal" enum in transports to fix the real issue. 


-- 
GitHub Notification of comment by akshayku
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/882#issuecomment-385822937 using your GitHub account

Received on Tuesday, 1 May 2018 23:46:09 UTC