Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Firefox-Embedded Selector 1.0"

(Architecture)
Line 1: Line 1:
== Architecture ==
 
For Higgins 1.0 the Web-based identity selector only supports integration with Firefox on Windows and Mac OSX. Support for other browsers and platforms is under active development.
 
 
===Firefox Architecture Variant ===
 
The Firefox implementation uses an embedded i-card selector within the [[Higgins Browser Extension]]. This has been available since 1.0M4.
 
[[Image:Higgins-deploy-web-ia-v45.JPG]]
 
 
 
== End-User Perspective ==
 
== End-User Perspective ==
 
Warning: Higgins has not yet been released, there are still lots of bugs and missing features.
 
Warning: Higgins has not yet been released, there are still lots of bugs and missing features.
Line 21: Line 14:
 
* If you go to the test sites listed under "Relying Party Sites" here: [[CardSpace Interop]] you should be able to sign in using the card (assuming that the claims supported by the card you used satisfy the relying site's policy).
 
* If you go to the test sites listed under "Relying Party Sites" here: [[CardSpace Interop]] you should be able to sign in using the card (assuming that the claims supported by the card you used satisfy the relying site's policy).
  
== Building ==
+
== Developer Perspective ==
 +
=== Architecture ===
 +
For Higgins 1.0 the Web-based identity selector only supports integration with Firefox on Windows and Mac OSX. Support for other browsers and platforms is under active development.
 +
 
 +
===Firefox Architecture Variant ===
 +
The Firefox implementation uses an embedded i-card selector within the [[Higgins Browser Extension]]. This has been available since 1.0M4.
 +
[[Image:Higgins-deploy-web-ia-v45.JPG]]
 +
 
 +
 
 +
 
 +
=== Building ===
 
This section describes the steps a developer would use to build deployable artifacts. The next section describes how to deploy them to create a runnable system.
 
This section describes the steps a developer would use to build deployable artifacts. The next section describes how to deploy them to create a runnable system.
  
Line 32: Line 35:
 
#* Constituent components include: [[RP Protocol Support]], [[I-Card Selector Service]], [[I-Card Registry]], [[I-Card Provider]], [[Token Service]], [[Identity Attribute Service]], Jena [[Context Provider]]
 
#* Constituent components include: [[RP Protocol Support]], [[I-Card Selector Service]], [[I-Card Registry]], [[I-Card Provider]], [[Token Service]], [[Identity Attribute Service]], Jena [[Context Provider]]
  
== Deploying ==
+
=== Deploying ===
 
This overall deployment configuration is comprised of these four sub-systems which must be built and deployed:
 
This overall deployment configuration is comprised of these four sub-systems which must be built and deployed:
 
# [[Deploying the Higgins Browser Extension for Firefox]]
 
# [[Deploying the Higgins Browser Extension for Firefox]]

Revision as of 11:20, 18 December 2007

End-User Perspective

Warning: Higgins has not yet been released, there are still lots of bugs and missing features.

Setup

To use this configuration you must:

  1. Install the Higgins Browser Extension into your browser.
  2. After re-starting your browser the setup wizard will help you set up your account on https://graceland.parityinc.net, the free test server run by Parity.

Functionality

You should now be able to:

  • Import Microsoft CardSpace-compatible managed cards from test sites listed under "Identity Providers" here: CardSpace Interop. You go to the card issuing site, create a .crd file for the card. If you click on the link to the .crd file, the browser extension will pop up and automatically import this into the web-based selector. If you have a .crd file on your hard drive, there is an import button in the i-card manager to manually import it into the selector.
  • If you click on the "mouse" button on the Higgins toolbar in Firefox the "i-card manager" web app will appear in your browser. You should be able to see your card(s) here.
  • You can select a card and delete it if you wish.
  • If you go to the test sites listed under "Relying Party Sites" here: CardSpace Interop you should be able to sign in using the card (assuming that the claims supported by the card you used satisfy the relying site's policy).

Developer Perspective

Architecture

For Higgins 1.0 the Web-based identity selector only supports integration with Firefox on Windows and Mac OSX. Support for other browsers and platforms is under active development.

Firefox Architecture Variant

The Firefox implementation uses an embedded i-card selector within the Higgins Browser Extension. This has been available since 1.0M4. Higgins-deploy-web-ia-v45.JPG


Building

This section describes the steps a developer would use to build deployable artifacts. The next section describes how to deploy them to create a runnable system.

This overall deployment configuration is comprised of the following sub-systems which must be built separately.

  1. Building the Higgins Browser Extension for Firefox
  2. Building the Higgins I-Card Manager Service
  3. Building the Higgins Identity Agent Service

Deploying

This overall deployment configuration is comprised of these four sub-systems which must be built and deployed:

  1. Deploying the Higgins Browser Extension for Firefox
  2. Deploying the Higgins I-Card Manager Service
  3. Deploying the Identity Agent Service

See Also

Links

Back to the top