Identity/Architecture/SignIntoBrowser: Difference between revisions

Identity/Architecture/SignIntoBrowser (view source)

329 bytes removed , 23 April 2012

668

edits

@@ Line 37: / Line 37: @@
 * a directory service that indicates the user's personalized services.
-=== ID-attached Services ===
+=== ID-connected Services ===
-An ID-attached service is a web-based service that takes a BrowserID assertion for login, then provides a particular service whose semantics are defined for that service category. The interface to that ID-attached service is via JavaScript <tt>MessageChannel</tt>: the user-agent loads the ID-attached-service endpoint URL in an (invisible) IFRAME and makes API calls to it using standard <tt>postMessage</tt> mechanics. The specifics of the <tt>MessageChannel</tt> calls are defined by the type of service.
+An ID-connected service is a web service that provides data and/or functions based on the user's identity. A service that stores a user's bookmarks (or passwords, or apps, or contacts) is one example of an ID-connected service.
-For example, an ID-attached Bookmarks Service implementation, be it from Mozilla or Delicious, provides a URL endpoint that expects certain bookmarks-specific calls over the <tt>MessageChannel</tt>.
+ID-connected services may authenticate users via Persona or any other authentication mechanism. Persona-authenticated services are easier to integrate into browser functionality, given the standard presentation of a Persona login assertion.
-(Why not REST? Because want to allow the service to do its own authentication and caching.)
 === User-Agent ===
 == Flow ==