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.
Difference between revisions of "Higgins Selector"
(→H1.1 All Selectors) |
(→Cloud-based Architecture) |
||
Line 19: | Line 19: | ||
=== Cloud-based Architecture === | === Cloud-based Architecture === | ||
− | + | The [[Cloud Selector 1.1]] under development for Higgins 1.1 has this architecture: | |
[[Image:Web-selector-1.1.102.png]] | [[Image:Web-selector-1.1.102.png]] |
Revision as of 11:30, 5 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Contents
Architecture
There are two kinds of selectors: client-based and cloud-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™.
Cloud-based Architecture
The Cloud Selector 1.1 under development for Higgins 1.1 has this architecture:
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:
- GTK and Cocoa Selector 1.0 - for Firefox (or other applications) on Linux, FreeBSD and OSX (client-based native code app)
- RCP Selector 1.0 - an Eclipse RCP Application (client-based Java app; requires JRE 1.4 or higher)
- Firefox-Embedded Selector 1.0 - for Firefox on Windows, Linux, and OSX (Requires hosted I-Card Service Component)
Higgins 1.1 Selector
Plan
See the Higgins 1.1 Selector section of the Higgins 1.1 Plan
H1.1 All Selectors
The following shows all variants of the Higgins 1.1 Selector in a single diagram:
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.