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 21:39, 4 October 2017
, 4 October 2017Language improvements
Mwobensmith (talk | contribs) m (Intro) |
Mwobensmith (talk | contribs) m (Language improvements) |
||
| Line 30: | Line 30: | ||
Web Authentication is the proposed W3C standard for creating an interface to validate a local, crytographically-signed message, with the purpose of enhancing a user's login credentials. | Web Authentication is the proposed W3C standard for creating an interface to validate a local, crytographically-signed message, with the purpose of enhancing a user's login credentials. | ||
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, | 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 | The browser is the broker between a web site and the USB device. The site implements the feature in JavaScript, which is the focus of the W3C spec. Firefox also implements a new USB interface for interacting with these hardware tokens, which is tangential to our implementation of the W3C Web Authentication spec. | ||
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 bugs and problems encountered by everyday Firefox users. | 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 bugs and problems encountered by everyday Firefox users. | ||
Currently, this feature is slated for Firefox 58, but | Currently, this feature is slated for Firefox 58, but this dependent on the status of the W3C spec. 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 | 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 is included in our QA team's build certification passes. | ||
== Scope == | == Scope == | ||