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"

Line 1: Line 1:
−
This is a new wiki page under development that will list the various deployment architectures/scenarios that the Higgins project intends to support
+
__NOTOC__
−
 
+
==Overview==
 +
Higgins [[Components]] (when complete) can be used as lego blocks to create:
 +
# '''Identity Agent''' - Requires the user to install the [[Higgins Browser Extension]] that is supported by a hosted Identity Agent service
 +
# '''Local Identity Agent''' - Requires the user to install the [[Higgins Browser Extension]] that is supported by a local rich client Identity Agent 
 +
# '''Identity Provider''' - CardSpace-compatible IdP/STS
 +
# '''Relying Party Libraries''' - Used by websites to add support for a variety of identity protocols
 +
===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)
 +
===Identity Agent===
 +
<to be written>
 +
===Local Identity Agent===
 +
<to be written>
 +
===Identity Provider===
 
{| 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"
Line 11: Line 34:
 
! width="10%" border="1" align="left" valign="top" | URL
 
! width="10%" border="1" align="left" valign="top" | URL
 
! width="10%" border="1" align="left" valign="top" | Owner
 
! width="10%" border="1" align="left" valign="top" | Owner
−
|-style="background:#d6dee9; color:black"
 
−
|colspan="4" | [[Nightly Component Builds]]
 
−
|SUSE
 
−
|Ant
 
−
|[[Nightly Component Builds PSF | psf]]
 
−
|n/a
 
−
|TBD
 
−
|build.eclipse.org
 
−
|[mailto:evgeniy@parityinc.net EvgeniyV]
 
 
|-style="background:#d6dee9; color:black"
 
|-style="background:#d6dee9; color:black"
 
|colspan="4" | [[CardSpace Managed Card Provider]]  
 
|colspan="4" | [[CardSpace Managed Card Provider]]  
Line 72: Line 86:
 
|n/a
 
|n/a
 
|n/a
 
|n/a
 +
|-
 +
|}
 +
.
 +
==Nightly Builds==
 +
Though not really "deployments", the Higgins project automatically builds some of the [[Components]] every night.
 +
{| 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="10%" border="1" align="left" valign="top" | Packaging
 +
! 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"
 
|-style="background:#d6dee9; color:black"
−
|colspan="4" | [[Local Higgins Service]]
+
|colspan="4" | [[Nightly Component Builds]]  
−
|
+
|SUSE
−
|n/a
+
|Ant
−
|n/a
+
|[[Nightly Component Builds PSF | psf]]
 
|n/a
 
|n/a
 
|TBD
 
|TBD
−
|TBD
+
|build.eclipse.org
−
|TBD
+
|[mailto:evgeniy@parityinc.net EvgeniyV]
−
|-style="background:#d6dee9; color:black"
+
−
|colspan="4" | [[Zero Footprint Higgins Service]]
+
−
|
+
−
|n/a
+
−
|n/a
+
−
|n/a
+
−
|TBD
+
−
|TBD
+
−
|TBD
+
 
|-
 
|-
 
|}
 
|}
 
.
 
.
−
 
−
===Columns===
 
−
* '''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)
 

Revision as of 11:21, 20 December 2006

Overview

Higgins Components (when complete) can be used as lego blocks to create:

  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

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)

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 not really "deployments", 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

.

Retrieved from "https://wiki.eclipse.org/index.php?title=Higgins/Solutions&oldid=21349"

Back to the top