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 1.1 Wishlist"

(Tentative Plan)
(IdAS-related components)
Line 12: Line 12:
  
 
===IdAS-related components===
 
===IdAS-related components===
 +
* Google Contacts CP - '''HIGH'''
 
* CDM 1.1 - '''HIGH''' - Paul will do this
 
* CDM 1.1 - '''HIGH''' - Paul will do this
 
* CDM Access control - '''priority'''
 
* CDM Access control - '''priority'''
Line 20: Line 21:
 
* JNDI/LDAP CP
 
* JNDI/LDAP CP
 
* Access Control CP?
 
* Access Control CP?
* Google Contacts CP - HIGH
+
* Open Social CP  
* Open Social CP - nice to have
+
* JDBC CP
* JDBC CP - nice to have
+
  
 
===STS-related components ===
 
===STS-related components ===

Revision as of 21:29, 31 January 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

This page is tentative. It needs to be rationalized with the existing plan here: Backlog. If we decide to make this page authoritative, then the Backlog pages should be deleted or linked to.

Tentative Plan

  • June date - Shadow Eclipse Release train if possible
  • Items are logged as
    • HIGH have high probability of being completed in upcoming sprints by June 09.
    • DONE are already or nearly completed.
    • priority are high value elements, but do not necessarily have resources devoted to developing them at this time.

IdAS-related components

  • Google Contacts CP - HIGH
  • CDM 1.1 - HIGH - Paul will do this
  • CDM Access control - priority
  • Restful Binding - priority
  • IdAS support for new CDM and initial access control - priority
  • Models as entities, especially data types - priority
  • RDF CP
  • JNDI/LDAP CP
  • Access Control CP?
  • Open Social CP
  • JDBC CP

STS-related components

  • SOAP1.2 - HIGH
  • WS-Trust 1.3 - HIGH
  • PPID algorithm support for v1.5 - DONE

Client

Selector Solutions

  • AIR Client and Server 1.1 - get all the code checked in using new AIR ICM UI in black & white
  • RCP - drop this for Higgins 1.1?
  • GTK and Cocoa Selector 1.0 - need to create a 1.1 page and update architecture diagrams with new HSS, new Synchronizing Card Store, etc.
  • Naming of the above with common branding: Higgins Selector for AIR, Higgins Selector for GTK - HIGH
  • Merging of selectors (part of Architecture Harmonization) - start moving to a common service, especially AIR and DigitalMe - HIGH
  • Positioning
    • Higgins Selector for MacOSX (AIR or Cocoa variant) - HIGH
    • Higgins Selector for Windows (AIR)
    • Higgins Selector for Linux (GTK) - already part of SUSE

Higgins Selector Switch

  • Windows
  • Linux
  • MacOSX - HIGH
  • Windows selector connector for CardSpace and AIR - DONE
  • Digital Me selector connectors (need MacOSX, Windows and Linux) - would be nice
  • Definitely decide on the API and requirements include UN/PW and OpenID and reliant party discovery (RPD)). Need user input in policy or runtime.

Higgins Server

  • What is the footprint of the above?
  • Note that IdAS would not be a Solution under this packaging.
  • TBD define the build targets.

New Card Types

  • UN/PW - would be nice - HIGH
  • OpenID - would be nice
  • R - would be nice

Infrastructure

  • Change Java version from 1.4.2 to 1.5? -Discussion followed by Doodle vote of committers - SELECTIVE
  • Breaking every jar into its own Eclipse project (relationship to Orbit) (Mary to ask for volunteer on the list.)** Internationalization of certain CPs - done
  • Evaluate how could internationalization the clients so that can outsource creating localized versions.
  • Automated testing based on buckminster builds
  • Paper on card-based authentication (Define card-based auth mechanism)??? where should this live, OASIS Security Services TC?

Back to the top