Skip to main content
Jump to: navigation, search

Difference between revisions of "Higgins/Solutions"

(RSS-SSE Test Relying Party Site)
(RSS-SSE Test Relying Party Site)
Line 70: Line 70:
  
 
===RSS-SSE Test Relying Party Site===
 
===RSS-SSE Test Relying Party Site===
 +
 
{| class="wikitable" style="text-align:left; width="100%" align="left" valign="top" border="1" cellpadding="5" cellspacing="0"
 
{| class="wikitable" style="text-align:left; width="100%" align="left" valign="top" border="1" cellpadding="5" cellspacing="0"
 
|-style="background:grey; color:black"
 
|-style="background:grey; color:black"

Revision as of 04:05, 1 February 2007

Overview

Higgins Components when complete (version 1.0) will be able to be used as lego blocks to construct a number of Deployment Scenarios each of which is documented (or will be!) on this page

Identity Provider

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

RSS-SSE Test Relying Party Site

Deployment Scenario OS Runtime Source & Build Binding Open URL Owner
RP Enablement n/a n/a n/a n/a TBD TBD
RSS-SSE Test Site ALL JVM 5.0, Tomcat 5.X WAR WS-Trust, WS-Transfer n/a site SergeiY

.

Identity Agent (in-browser selector, hosted IdA)

Identity Agent (rich client selector, hosted IdA)

  • Requires the user to install the Higgins Browser Extension (HBX) and the ISS Client UI rich client card selector. ISS Client UI relies on a hosted Identity Agent service

Identity Agent (rich client selector, local IdA)

  • Requires the user to install the Higgins Browser Extension (HBX) and the ISS Client UI rich client card selector. ISS Client UI relies on a local Identity Agent service.

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 Source & Build 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