- From: Brad Hill via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jul 2017 16:49:37 +0000
- To: public-webauthn@w3.org
Even for a bound authenticator, how do I know if a given person arriving at my service in a browser actually has an authenticator available? My request is that: 1) Be able to determine if a given person has an authenticator available they want to use, so that we can promote the setup flow non-intrusively. (e.g. put an install banner across the top of the screen) I don't want to just randomly call create credential and trigger some kind of modal experience if that's not what the person is in the context of doing at the time. People very rarely visit their security settings without some kind of soft prompting. 2) Be able, when the user is in the context of setting up their authenticator and starting the registration process, to understand enough about the characteristics to present appropriate instructions. On Fri, Jul 7, 2017 at 9:22 AM Rolf Lindemann <notifications@github.com> wrote: > I think this is mainly relevant in the case of roaming authenticators as > bound authenticator would always be responsive (to a create call). > > But even without actively advertising the support for access to a roaming > Authenticator on the platform to the RP JS Code, the Browser could remember > that it has seen a roaming Authenticator before and could ask the user > whether to use/insert it or to say no authenticator available (when > encountering a create call for a WebAuthn credential). > > So this could potentially be addressed by implementation guidance (even > without an API change). > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webauthn/issues/503#issuecomment-313728182>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ACFbcBXClZCllMY0NZSKc2kAWuvOBi_1ks5sLls9gaJpZM4OQW-f> > . > -- GitHub Notification of comment by hillbrad Please view or discuss this issue at https://github.com/w3c/webauthn/issues/503#issuecomment-313734787 using your GitHub account
Received on Friday, 7 July 2017 16:49:43 UTC