Higgins/Solutions
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 |
Identity Agent (in-browser selector, hosted IdA)
- Requires the user to install the Higgins Browser Extension (HBX). HBX relies on a hosted Identity Agent (IdA) service
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.
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 |
.
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:
- Deployment Scenario - link to wiki page describing deployment scenario
- Included Component - see Components
- Included plug-in (if applicable)
- Consumed non-Higgins service (if any)
- Included plug-in (if applicable)
- Included Component - see Components
- 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)