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)
Line 1: Line 1:
 
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.
 
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 ===
+
==Higgins Identity Agent ==
 
An identity agent is an end-user application that allows a user to accept [http://en.wikipedia.org/wiki/I-card 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.  
 
An identity agent is an end-user application that allows a user to accept [http://en.wikipedia.org/wiki/I-card 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.  
  
Line 11: Line 11:
 
* [[Eclipse-based Identity Agent]] - for Eclipse RCP Applications (runs entirely on local machine)
 
* [[Eclipse-based Identity Agent]] - for Eclipse RCP Applications (runs entirely on local machine)
  
===Services===
+
==Services==
 
* [[STS/IdP Deployment]] - STS/IdP service
 
* [[STS/IdP Deployment]] - STS/IdP service
 
* [[IdAS Deployment]] - Identity Attribute Service
 
* [[IdAS Deployment]] - Identity Attribute Service
 
* [[RP Site Deployment]] - Relying Party site
 
* [[RP Site Deployment]] - Relying Party site
  
===Nightly Builds===
+
==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.
 
* [[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===
+
==Higgins-based Services and Apps==
 
This section lists known services and apps developed external to the Higgins project, but based on Higgins [[Components]].
 
This section lists known services and apps developed external to the Higgins project, but based on Higgins [[Components]].
 
* [[Bandit STS/IdP Deployment]] - Higgins-based STS/IdP service
 
* [[Bandit STS/IdP Deployment]] - Higgins-based STS/IdP service

Revision as of 17:34, 8 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 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 identity agent 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 agent deployment configurations that we support:

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