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/Solutions"

(Higgins Identity Agent)
(Higgins Identity Agent)
Line 8: Line 8:
 
Here are the four deployment configurations that the Higgins project supports:
 
Here are the four deployment configurations that the Higgins project supports:
  
Hosted service:
+
Web-based:
 
* [[H1 Identity Agent Deployment]] - for Firefox or IE on Windows, Linux, and OSX (local browser extention and a hosted agent service)
 
* [[H1 Identity Agent Deployment]] - for Firefox or IE on Windows, Linux, and OSX (local browser extention and a hosted agent service)
Standalone:
+
Client-based:
 
* [[H2 Identity Agent Deployment]] - for Firefox (or other applications) on Linux, FreeBSD and OSX (runs entirely on local machine)
 
* [[H2 Identity Agent Deployment]] - for Firefox (or other applications) on Linux, FreeBSD and OSX (runs entirely on local machine)
 
* [[H3 Identity Agent Deployment]] - for Firefox on Linux, OSX, and Windows (runs entirely on local machine)
 
* [[H3 Identity Agent Deployment]] - for Firefox on Linux, OSX, and Windows (runs entirely on local machine)
Eclipse plug-in:
+
Java client-based:
 
* [[H4 Identity Agent Deployment]] - for Eclipse RCP Applications (runs entirely on local machine)
 
* [[H4 Identity Agent Deployment]] - for Eclipse RCP Applications (runs entirely on local machine)
  

Revision as of 14:23, 3 October 2007

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

Higgins Identity Agent

An identity agent is an end-user application that allows a user to accept i-cards from card issuing sites (known in the identity industry 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 the Higgins IA 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 four deployment configurations that the Higgins project supports:

Web-based:

Client-based:

Java client-based:

Services

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.

Higgins-based Services and Apps

This section lists known services and apps developed external to the Higgins project, but based on Higgins Components.

Links

Back to the top