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 "Higgins Selector"

(Higgins 1.0 Selectors)
(Higgins 1.1 Selectors)
Line 35: Line 35:
 
Goals:
 
Goals:
  
* All client-based selector solutions should share a common set of Higgins Browser Extensions (aka HBX) --one for each supported browser.
+
* All client-based selector solutions should share a common [[Higgins Browser Extension]] (aka HBX) for each supported browser.
* Add support for non-I-Card authentication methods into HBX. We’re interested in both OpenID and plain old username/password. There’s been discussions within OSIS, and with members of the IDIB project about collaborating on this.
+
* Add support for non-I-Card authentication methods into HBX. We’re interested in both OpenID and plain old username/password. There’ve been discussions within OSIS, and with members of the IDIB project about collaborating on this.
 
* We have a Higgins Selector Switch (and related components) for Windows. We neeed to port HSS to Mac OSX (and preferably Linux too.)
 
* We have a Higgins Selector Switch (and related components) for Windows. We neeed to port HSS to Mac OSX (and preferably Linux too.)
  

Revision as of 23:50, 16 March 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}} Higgins site card1.png


Architecture

There are two kinds of selectors: client-based and web-based.

Client-based Architecture

The core of the client-based selector is surrounded by two ancillary components: The HBX and the HSS:

  • Higgins Browser Extension – interacts with the current webpage and requests/retrieves identity information from the selector via the Higgins Selector Switch.
  • Higgins Selector Switch – launches the user's chosen selector. The HSS Manager provides a UI to allow the user to set their default selector (e.g. CardSpace or one of the Higgins selectors, etc.). The HSS Launcher makes sure that the HSS service is running as a background process.
  • Selector – client code that manages identity information using the I-Card metaphor. A selector is used to manage the users's identity-related interactions (including authentication) with RPs. At the user’s option, the HSS can either launch one of the Higgins selectors or CardSpace™.

Higgins-client-1.1.102.png

Web-based Architecture

Under development for Higgins 1.1 the Web Selector has this architecture:

Web-selector-1.1.102.png

Higgins 1.0 Selectors

In Higgins 1.0 we made partial progress towards the architecture diagrammed above. In 1.0 we hadn’t yet invented the concept of a selector switch, and the three selector solutions use different browser extensions. See each of the following (client-based) selector solutions for details:

Higgins 1.1 Selectors

Goals:

  • All client-based selector solutions should share a common Higgins Browser Extension (aka HBX) for each supported browser.
  • Add support for non-I-Card authentication methods into HBX. We’re interested in both OpenID and plain old username/password. There’ve been discussions within OSIS, and with members of the IDIB project about collaborating on this.
  • We have a Higgins Selector Switch (and related components) for Windows. We neeed to port HSS to Mac OSX (and preferably Linux too.)

H1.1 Selectors:

How to use a Selector and I-Cards

  • You get cards from web sites. Or you can create your own.
  • You install a wallet-like software app called a selector that lets you see and manage them.
  • By clicking on a card you can log into sites. No more passwords.
  • By clicking on a card you express yourself. No more filling in forms.
  • You can share cards with friends and businesses you trust.
  • Some cards create permanent connections to your friends, communities and businesses.

Back to the top