canmove, Confirmed users
409
edits
Services/Sync/Features/BrowserID Authentication: Difference between revisions
Jump to navigation
Jump to search
m
Services/Sync/Features/BrowserID Authentication (view source)
Revision as of 20:45, 28 December 2011
, 28 December 2011no edit summary
m (add definitions) |
mNo edit summary |
||
| Line 12: | Line 12: | ||
|Feature requirements=# New Sync users do not need to explicitly create a Mozilla Services account, but instead create BrowserID accounts (if they don't have one already) | |Feature requirements=# New Sync users do not need to explicitly create a Mozilla Services account, but instead create BrowserID accounts (if they don't have one already) | ||
# HTTP requests to the Sync server are authenticated via something derived from BrowserID, not by the user's original credentials. | # HTTP requests to the Sync server are authenticated via something derived from BrowserID, not by the user's original credentials. | ||
# The HTTP authentication mechanism should be designed in such a way it can be reused by not only additional Mozilla services, but also by random people on the Internet. | # The HTTP authentication mechanism should be designed in such a way it can be reused by not only additional Mozilla services, but also by random people on the Internet, for both large and small services. | ||
|Feature non-goals=This feature does *not* involve changing Sync's data encryption model (currently using a cryptographically secure randomly generated private key for client-side encryption). It only involves changing the mechanism by which new user accounts are handled and how Sync HTTP requests are authenticated. | |Feature non-goals=This feature does *not* involve changing Sync's data encryption model (currently using a cryptographically secure randomly generated private key for client-side encryption). It only involves changing the mechanism by which new user accounts are handled and how Sync HTTP requests are authenticated. | ||
}} | }} | ||