Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Org.eclipse.higgins.hbx"

(Plan)
Line 4: Line 4:
 
[Note: At present this Higgins service is hosted, but in the future we will also support a "local" Higgins service installed on the same machine as your browser.]
 
[Note: At present this Higgins service is hosted, but in the future we will also support a "local" Higgins service installed on the same machine as your browser.]
  
==Plan==
+
==Operation==
  
The current version of HBX has some preliminary CardSpace, RSS-P, and HTML (form-fill/screen-scrape) support. We will soon integrate a [[Token Service]] to create self-signed tokens ([[Digital Identity|Digital Identities]]).  
+
The current version of the Higgins Extension has varying levels of support for what we will loosely call RP '''interaction types.''' These interactions begin after the browser has done an HTTP GET on some page. The Higgins Extension parses the HTML searching for markers that indicate what type of interaction the RP site supports.
  
'''I-Card Selector:''' HBX does not yet have an "Identity Selector" user interface, but that is also in the works. Although the policy is controlled by the user, the ''default'' policy that we're considering is that the Identity Selector UI appears only if ''identifying'' information about the user is required by the Relying Party. If the information required is non-identifying then the user can define one or more identity information templates containing this non-identifying information, and release the required subset of it to the Relying Party without bothering the user by displaying the Identity Selector.
+
====Kinds of RP Interactions====
 +
 
 +
If it finds CardSpace-compatible markers, then this indicates that the RP site supports CardSpace-compatible authentication (sign-in). If it finds RSS-P markers then the site allows the user to "project" identity information (usually non-identifiying attributes) to the site, e.g. to express the user's "shopping" persona (preferences, etc.). If the site is one for which the user's Higgins Service has an "HTML Card", then the Higgins Extension will attempt to fill in forms on that site as well as scrape the users's own personal data from site.
  
 
==HBX version 0.5.X==
 
==HBX version 0.5.X==

Revision as of 11:31, 14 November 2006

Overview

The Higgins Browser Extension (aka HBX) is a Firefox extension written in Javascript. When Higgins Extension is installed and your browser lands on a "relying party" (RP) site, HBX manages authentication and other kinds of identity-related interactions between the RP site and the Higgins service.

[Note: At present this Higgins service is hosted, but in the future we will also support a "local" Higgins service installed on the same machine as your browser.]

Operation

The current version of the Higgins Extension has varying levels of support for what we will loosely call RP interaction types. These interactions begin after the browser has done an HTTP GET on some page. The Higgins Extension parses the HTML searching for markers that indicate what type of interaction the RP site supports.

Kinds of RP Interactions

If it finds CardSpace-compatible markers, then this indicates that the RP site supports CardSpace-compatible authentication (sign-in). If it finds RSS-P markers then the site allows the user to "project" identity information (usually non-identifiying attributes) to the site, e.g. to express the user's "shopping" persona (preferences, etc.). If the site is one for which the user's Higgins Service has an "HTML Card", then the Higgins Extension will attempt to fill in forms on that site as well as scrape the users's own personal data from site.

HBX version 0.5.X

Reference

http://xmldap.blogspot.com/2006/05/firefox-identity-selector.html - Chuck Mortimore's Firefox extension. Chuck and the Higgins team have collaborated a bit on the development of our respective extentions.

See Also

Back to the top