Confirmed users
651
edits
Security/QA/TestPlans/Web Authentication: Difference between revisions
Jump to navigation
Jump to search
m
Security/QA/TestPlans/Web Authentication (view source)
Revision as of 22:09, 4 October 2017
, 4 October 2017Lots of enhancements
Mwobensmith (talk | contribs) m (Created) |
Mwobensmith (talk | contribs) m (Lots of enhancements) |
||
| Line 7: | Line 7: | ||
! Name !! Title !! Department !! Approval Date !! Method | ! Name !! Title !! Department !! Approval Date !! Method | ||
|- | |- | ||
| | | Ryan VanderMuelen || QA Manager || Product Integrity || Date || Email | ||
|- | |- | ||
| JC Jones || Software Engineer || Engineering || Date || Email | | JC Jones || Software Engineer || Engineering || Date || Email | ||
| Line 28: | Line 28: | ||
= Overview = | = Overview = | ||
== Purpose == | == Purpose == | ||
Web Authentication is the proposed W3C standard for creating an interface to validate a local, cryptographically-signed message. | Web Authentication - or "WebAuthN" - is the proposed W3C standard for creating an interface to validate a local, cryptographically-signed message. | ||
What this means in simple language - for Firefox - is the ability for a user to employ a USB token during a login process as another factor of authentication, in addition to typical methods, such as a password. | What this means in simple language - for Firefox - is the ability for a user to employ a USB token during a login process as another factor of authentication, in addition to typical methods, such as a password. | ||
The browser is the broker between a web site and the USB device. The site implements the feature in JavaScript, which is | The browser is the broker between a web site and the USB device. The site implements the feature in JavaScript, which is outlined within the W3C spec. Firefox also implements new USB support for interacting with these hardware tokens, which is tangential to our implementation of the spec itself. | ||
We are interested in testing both JS API and USB support. In addition, we are most concerned with integration scenarios, which often surface the most | We are interested in testing both JS API and USB support. In addition, we are most concerned with integration scenarios, which often surface the most problems likely to be encountered by everyday Firefox users. | ||
The exact release of Firefox is dependent on the status of the W3C spec, which is nearing finalization. Regardless, the vast majority of this feature's test requirements is captured here and will not change. | |||
The goal set forth in this document is to outline a test strategy that will be implemented up until the feature has been shipped in a major release of Firefox. At that point, it is expected that the suite of manual test cases | The goal set forth in this document is to outline a test strategy that will be implemented up until the feature has been shipped in a major release of Firefox. At that point, it is expected that the suite of manual test cases will be included in our QA team's build certification passes. | ||
== Scope == | == Scope == | ||
| Line 74: | Line 74: | ||
=== Out of Scope === | === Out of Scope === | ||
* Software token is unsupported, for now. | * Software token is unsupported, for now. | ||
* Yubico | * Yubico and FIDO have provided us with some USB keys to test with, but the full range of potentially supported keys is not something we have available to us. | ||
* Other hardware vendors will need to certify their products on Firefox, as we cannot guarantee coverage on all third party USB tokens. | * Other hardware vendors will need to certify their products on Firefox, as we cannot guarantee coverage on all third party USB tokens. | ||
* This feature is not currently supported on Fennec. | * This feature is not currently supported on Fennec. | ||