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

(Conventions Used)
(See Also)
Line 103: Line 103:
 
|}
 
|}
 
.
 
.
 +
===Conventions Used===
 +
The tables on this wiki page have the following column structure:
 +
# '''Deployment Scenario''' - link to wiki page describing deployment scenario
 +
#* '''Included Component''' - see [[Components]]
 +
#** Included plug-in (if applicable)
 +
#*** Consumed non-Higgins service (if any)
 +
# '''OS''' - OS that this component requires. Put in parens the OS number if more than OS instance is involved
 +
# '''Runtime''' - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.)
 +
# '''Packaging''' - how will component be made available for installation
 +
# '''Binding''' - how will externally consumed services of deployment scenario be consumed
 +
# '''Open''' - open enhancements and bugs (Bugzilla)
 +
# '''URL''' - endpoint that hosts a test service (hosted by Eclipse Foundation)
 +
# '''Owner''' - person with overall responsibility for this deployment scenario (not individual components)
 +
 
==See Also==
 
==See Also==
 
* [http://eclipse.org/higgins Higgins Home]
 
* [http://eclipse.org/higgins Higgins Home]

Revision as of 23:18, 31 January 2007

Overview

Higgins Components when complete will be able to be used as lego blocks to construct the following:

  1. Identity Agent - Requires the user to install the Higgins Browser Extension that is supported by a hosted Identity Agent service
  2. Local Identity Agent - Requires the user to install the Higgins Browser Extension that is supported by a local rich client Identity Agent
  3. Identity Provider - CardSpace-compatible IdP/STS
  4. Relying Party Libraries - Used by websites to add support for a variety of identity protocols


Identity Agent

<to be written>

Local Identity Agent

<to be written>

Identity Provider

Deployment Scenario OS Runtime Packaging Binding Open URL Owner
CardSpace Managed Card Provider n/a n/a psf n/a TBD TBD TomD
Token Service SUSE(1) JVM 5.0, Tomcat X.X WAR WS-Trust, WS-Transfer n/a n/a n/a
Identity Attribute Service SUSE(1) ? ? ? n/a n/a n/a
LDAP Context Provider SUSE(1) ? ? ? n/a n/a n/a
OpenLDAP Server SUSE(2) ? ? ? n/a n/a n/a

.

Nightly Builds

Though certainly not a "deployment" in the usual sense, the Higgins project automatically builds some of the Components every night.

Deployment Scenario OS Runtime Packaging Binding Open URL Owner
Nightly Component Builds SUSE Ant psf n/a TBD build.eclipse.org EvgeniyV

.

Conventions Used

The tables on this wiki page have the following column structure:

  1. Deployment Scenario - link to wiki page describing deployment scenario
    • Included Component - see Components
      • Included plug-in (if applicable)
        • Consumed non-Higgins service (if any)
  2. OS - OS that this component requires. Put in parens the OS number if more than OS instance is involved
  3. Runtime - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.)
  4. Packaging - how will component be made available for installation
  5. Binding - how will externally consumed services of deployment scenario be consumed
  6. Open - open enhancements and bugs (Bugzilla)
  7. URL - endpoint that hosts a test service (hosted by Eclipse Foundation)
  8. Owner - person with overall responsibility for this deployment scenario (not individual components)

See Also

Back to the top