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"

Line 4: Line 4:
 
This page describes the Higgins Card Selectors. For an introduction, see the the [http://informationcard.net Information Card Foundation's] [http://informationcard.net/quick-overview quick overview of cards and selectors].
 
This page describes the Higgins Card Selectors. For an introduction, see the the [http://informationcard.net Information Card Foundation's] [http://informationcard.net/quick-overview quick overview of cards and selectors].
  
==Architecture==
+
==Introduction==
  
There are two kinds of selectors: client-based and cloud-based.
+
A card selector is a piece of software that runs on a computer or mobile device. The user can get cards from card issuing websites and can store them in this selector in much the same way a person puts business, library, loyalty and payment cards in their wallet.
  
=== Client-based Architecture ===
+
* 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.
  
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.
+
[[Image:Higgins-selector-overview.png]]
* '''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™.
+
  
[[Image:Higgins-client-1.1.102.png]]
+
Some selector clients take advantage of cloud-based services. These services include:
 
+
:;I-Card Service: ''(Higgins 1.0 & 1.1)'' some selectors are designed as "thin clients" that only implement the user interface and rely on a hosted I-Card Service in order to function
=== Cloud-based Architecture ===
+
:;CardSync: ''(Higgins 1.1)'' makes sure that all of your cards are available across all of your computers and mobile devices
 
+
:;Identity Data Service(IDS): ''(Higgins 1.1 only)'' stores self asserted identity data and makes it available for data sharing with others. It also provides data gateway services to connect the client selector with a variety of back end data stores
The [[Cloud Selector 1.1]] under development for Higgins 1.1 has this architecture:
+
:;Cloud Selector: ''(Higgins 1.1 only)'' makes your cards available as OpenIDs
 
+
[[Image:Web-selector-1.1.102.png]]
+
  
 
==Higgins 1.0 Selector ==
 
==Higgins 1.0 Selector ==
Line 36: Line 36:
 
=== Plan ===
 
=== Plan ===
 
See the [http://wiki.eclipse.org/Higgins_1.1_Plan#Higgins_Selector Higgins 1.1 Selector section of the Higgins 1.1 Plan]
 
See the [http://wiki.eclipse.org/Higgins_1.1_Plan#Higgins_Selector Higgins 1.1 Selector section of the Higgins 1.1 Plan]
 
===All Selectors ===
 
 
The following shows all variants (except the [[iPhone Selector 1.1]]) of the Higgins 1.1 Selector in a single diagram:
 
 
[[Image:All-selectors-1.1.104.png]]
 
 
Notes:
 
* In the above, the "IDS" is a web binding over IdAS (current implementation is XDI only) --it probably should be shown running in its own process
 
 
==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.
 

Revision as of 21:40, 10 July 2009

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

This page describes the Higgins Card Selectors. For an introduction, see the the Information Card Foundation's quick overview of cards and selectors.

Introduction

A card selector is a piece of software that runs on a computer or mobile device. The user can get cards from card issuing websites and can store them in this selector in much the same way a person puts business, library, loyalty and payment cards in their wallet.

  • 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.


Higgins-selector-overview.png

Some selector clients take advantage of cloud-based services. These services include:

I-Card Service
(Higgins 1.0 & 1.1) some selectors are designed as "thin clients" that only implement the user interface and rely on a hosted I-Card Service in order to function
CardSync
(Higgins 1.1) makes sure that all of your cards are available across all of your computers and mobile devices
Identity Data Service(IDS)
(Higgins 1.1 only) stores self asserted identity data and makes it available for data sharing with others. It also provides data gateway services to connect the client selector with a variety of back end data stores
Cloud Selector
(Higgins 1.1 only) makes your cards available as OpenIDs

Higgins 1.0 Selector

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 Selector

Plan

See the Higgins 1.1 Selector section of the Higgins 1.1 Plan

Back to the top