- From: 李林哲 via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Jan 2020 03:05:39 +0000
- To: public-webauthn@w3.org
Thanks, to all of you. > However, there would be practical deployment issues such as users having to register credential(s) with each "named-by-ip-address" server rather than being able to have a credential that is honored in "all of a domain", e.g., honored in all subdomains of example.com. In my practice, most company has not adopted unified 3A （Authentication, Authorization and Accounting). And the IT foundation of these company built on commercial off-the-shelf (COTS) productions. In such a situation. These product must take care of there self's Authentication. (And the end user must take care of their password either.) The `Webauthn` adoption of these COTS product will help to change this situation. And products will not accept must be accessed by domain (And they could not predict which domain). Hope this will help. Thanks for your time. -- GitHub Notification of comment by slayercat Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1358#issuecomment-573274224 using your GitHub account
Received on Saturday, 11 January 2020 03:05:40 UTC