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

Component Deliverables

Revision as of 13:13, 12 October 2006 by Paul.socialphysics.org (Talk | contribs) (IdAS)

Release 1.0 Components and Status

This page lists the components envisioned for Higgins v1.0.

Clients

Higgins Browser Extension

  • Description: Higgins Browser Extension
  • Status: Firefox versions since M0.4
  • Language
    1. Javascript and XUL (Firefox)
    2. TBD (IE)
    3. TBD (Safari)
  • Packaging:
    1. Firefox browser extension
    2. IE plugin
    3. Safari plugin
  • Deployment (End user download and installation):
    1. Firefox HBX running on Windows, OSX, Suse, Red Hat, Debian, Ubuntu
    2. Internet Exporer 6 HBX running on Windows
    3. Safari HBX running on OSX

Core Components

I-Card Manager

  • Description: I-Card Manager
  • Status: working prototype shown in June; need to refactor/rewrite per current Higgins architecture
  • Language: Java
  • Packaging: WAR or OSGI bundle
  • Deployment: JSP servlet on remote Tomcat or OSGI server

HBX Support

  • Description: HBX Support
  • Status: working prototype for RSS-P and Scrape&Fille shown in June; need to refactor
  • Language: Java
  • Bindings: WSDL/SOAP
  • Packaging: WAR or OSGI bundle
  • Deployment: JSP servlet on remote Tomcat or OSGI server

ISS Web UI

  • Description: ISS Web UI
  • Status:
  • Language: Java
  • Packaging: WAR or OSGI bundle
  • Deployment: JSP servlet on remote or local appserver
  • Client Deployment:
    • JSP on Tomcat or OSGI app server
  • Server Deployment:
    • JSP on Tomcat or OSGI app server

ISS Client UI

  • Description: ISS Client UI
  • Status: dev work will start in M0.7
  • Language: Java using Eclipse Rich Client Platform
  • Packaging:
    • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {Bindings: C, C++} * {RPM, Debian}
    • OSX: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * TBD
    • Windows: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * MSI
    • Java: OSGI bundle
  • Client Deployment:

RP Enablement

  • Description: RP Enablement
  • Status:
  • Languages: Java, PHP, Python, Ruby
  • Packaging:
  • Deployment: Libraries for integration into Relying Party sites.

I-Card Selector Service (ISS)

  • Description: I-Card Selector Service
  • Status: preliminary API, early code in M0.6
  • Language: Java
  • Packaging:
    • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {Bindings: C, C++} * {RPM, Debian}
    • OSX: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * TBD
    • Windows: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * MSI
    • Java: OSGI bundle
    • Java: WAR
  • Client Deployment:
  • Server Deployment:
    • JSP on Tomcat or OSGI app server

I-Card Registry

  • Description: I-Card Registry
  • Status: first code in M0.6
  • Language: Java
  • Packaging:
    • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {Bindings: C, C++} * {RPM, Debian}
    • OSX: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * TBD
    • Windows: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * MSI
    • Java: OSGI bundle
    • Java: WAR
  • Client Deployment:
  • Server Deployment:
    • JSP on Tomcat or OSGI app server

I-Card Providers

  1. CardSpace I-Card Provider
    • Build: GCJ Binary: {CPU: x86, ?} * {bindings: C, C++}; Java: Eclipse plugin
    • Tested I-Cards:
      • live.microsoft.net STS i-card
      • PingIdentity STS i-card
      • Kim's blog i-card
  2. RSS-P I-Card Provider
    • Build: GCJ Binary: {CPU: x86, ?} * {bindings: C, C++}; Java: Eclipse plugin
  3. OpenID-H I-Card Provider
    • Build: GCJ Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin

Attribute-Claim Mapping

  • Build: Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin

Token Service

  • Description: Token Service
  • STS
    • Status: working prototype; waiting on legal
    • Language: Java
    • Packaging:
      • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {Bindings: C, C++} * {RPM, Debian}
      • OSX: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * TBD
      • Windows: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * MSI
      • Java: JAR
      • Java: OSGI bundle
      • Java: WAR
    • Client Deployment:
    • Server Deployment:
      • JSP on Tomcat or OSGI app server

Token Providers

  • SAML Token Provider
  • un/pw Token Provider [working prototype; waiting on checkin]
  • idemix Token Provider [working prototype; waiting on checkin]
  • x509 Token Provider --not sure about this (at least able to validate and cancel these)

IdAS

  • Description: Identity Attribute Service
  • Status: Available from M0.5+
  • Language: Java
  • Bindings: Java, C, C++, WSDL/SOAP
  • Packaging:
    • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {RPM, Debian}
    • OSX: {GCJ Binaries: {x86,?} * * TBD
    • Windows: {GCJ Binaries: {x86,?} * MSI
    • Java: OSGI bundle
    • Java: WAR
  • Client Deployment:
    • TBD
  • Server Deployment:
    • JSP on Tomcat or OSGI app server

IdAS Context Providers

  1. LDAP provider
    • Status: under development M0.5..M0.6
    • Build: GCJ Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin
  2. XML-File based provider
    • Status: under development in M0.5..M0.6
    • Build: GCJ Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin
  3. Jena/HSQLDB provider
    • Status: under development in M0.5..M0.6
    • Build: GCJ Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin
  4. RSS-P (uses Jena/HSQLDB) provider
    • Status: under development in M0.5..M0.6
    • Build: GCJ Binary: {CPU: x86,?} * {bindings: C, C++}; Java: Eclipse plugin
  5. SAML Token Wrapper provider
  6. x509 Token Wrapper provider

Build Targets

Each of the above needs to be automatically built (with javadoc) and automatically tested (on build.eclipse.org) in three variants (daily, stable, release).

See Also

Back to the top