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

Higgins/Solutions

< Higgins
Revision as of 16:37, 20 December 2007 by Paul.socialphysics.org (Talk | contribs) (Higgins-based Solutions)

A Solution is a specific combination of Higgins Components that, when assembled and deployed, results in either an infrastructure-level service, or an end-user application.

Higgins Supported Solutions

This section describes the solutions developed by the Higgins team.

End-user Solutions: Identity Selectors

An identity selector is an end-user application that allows a user to accept i-cards from card issuing sites (known as Identity Providers or IdPs), create self-issued i-cards, manage the user's set of cards (a bit like a wallet), and to use these cards to authenticate to relying sites, or to local applications. These i-cards are visualized as card icons in a user interface that allows the user to review, manage and in some cases edit some of the information associated with the card.

The long term plan is that these selectors will support all of the major identity protocols and run on all popular platforms. In the past year we have worked mostly on interoperability with Microsoft CardSpace-compatible card issuing and relying sites, systems and services as well as with OpenID OPs and relying sites.

Here are the three identity selector solutions that we support:

Developer Solutions

Higgins 1.0 will support the following solutions:


Higgins-based Solutions

This section lists solutions developed external to the Higgins project, but based on Higgins Components.

Misc

Nightly Builds

  • Automated Builds - not a deployment configuration in the usual sense; the Higgins project automatically builds some (and soon all) of the Components every night.

Links

Back to the top