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"

(Nightly Builds)
Line 73: Line 73:
 
* Deployment owner: SergeyY
 
* Deployment owner: SergeyY
 
* <to be described>
 
* <to be described>
 +
{| class="wikitable" style="text-align:left; width="100%" align="left" valign="top" border="1" cellpadding="5" cellspacing="0"
 +
|-style="background:grey; color:black"
 +
! width="30%" border="1" align="left" valign="top" colspan="4" | Deployment Scenario
 +
! width="10%" border="1" align="left" valign="top" | OS
 +
! width="10%" border="1" align="left" valign="top" | Runtime
 +
! width="15%" border="1" align="left" valign="top" | Source & Build
 +
! width="10%" border="1" align="left" valign="top" | Binding
 +
! width="10%" border="1" align="left" valign="top" | Open
 +
! width="10%" border="1" align="left" valign="top" | URL
 +
! width="10%" border="1" align="left" valign="top" | Owner
 +
|-style="background:#d6dee9; color:black"
 +
|colspan="4" | [[RP Enablement]]
 +
|n/a
 +
|n/a
 +
|[[Nightly Component Builds PSF | psf]]
 +
|n/a
 +
|TBD
 +
|build.eclipse.org
 +
|
 +
|-
 +
|
 +
|colspan="3" | [[Token Service]]
 +
|ALL
 +
|JVM 5.0, Tomcat X.X
 +
|WAR
 +
|WS-Trust, WS-Transfer
 +
|n/a
 +
|n/a
 +
|[mailto:sergey@parityinc.net SergeiY]
 +
|-
 +
|}
 +
.
  
 
===Identity Agent (in-browser selector, hosted IdA)===
 
===Identity Agent (in-browser selector, hosted IdA)===

Revision as of 03:31, 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 owner: SergeyY
  • <to be described>
Deployment Scenario OS Runtime Source & Build Binding Open URL Owner
RP Enablement n/a n/a psf n/a TBD build.eclipse.org
Token Service ALL JVM 5.0, Tomcat X.X WAR WS-Trust, WS-Transfer n/a n/a 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