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"

(Overview)
Line 10: Line 10:
 
** '''DONE''' are already or nearly completed.  
 
** '''DONE''' are already or nearly completed.  
 
** '''priority''' are high value elements, but do not necessarily have resources devoted to developing them at this time.
 
** '''priority''' are high value elements, but do not necessarily have resources devoted to developing them at this time.
 +
* Upcoming milestone: [[1.1M7]]
  
 
== Website ==
 
== Website ==

Revision as of 09:43, 28 March 2009

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

Higgins logo 76Wx100H.jpg

This page lists everything that remains to be done for Higgins 1.1. Many of the items on this page have been pulled from the overall long term wishlist here: Backlog and sub-backlog pages linked from it (e.g. Website Backlog, etc.). Our process should be to describe and discuss the tasks here. When we know which milestone they will belong to we create bugzilla items for them appropriately.

Overview

  • June release date for Higgins 1.1
  • 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.
  • Upcoming milestone: 1.1M7

Website

New solution names

  • Selector Mac-AIR - includes Selector Client Mac-AIR, HSS Mac, HBX FF
  • Selector Mac-COC - includes Selector Client Mac-COC, HSS Mac, HBX FF
  • Selector Win-AIR - includes Selector Client Win-AIR, HSS Win, HBX FF, HBX IE
  • Selector Win-GTK - includes Selector Client Win-AIR, HSS Win, HBX FF, HBX IE
  • Selector Linux-GTK - includes Selector Client Lin-GTK, HSS Lin, HBX FF
  • Web Selector Java-GWT

New Components Page(s)

  • Instead of all components for Higgins 1.0 and Higgins 1.1 mixed together on a single page, we create two separate pages: Components 1.0 and Components 1.1
  • The appearance of each of the two Components pages would be the same as today's single Components page with these exceptions:
    • The "H1.0" and "H1.1" columns (with LEDs) are no longer needed
    • We create the two replacement pages as .PHP web pages NOT wiki pages. This has two advantages (i) the current Components page is the only wiki page on the site to which the new style sheet can't be used (rather than debug the problem with the wiki templates and the .css we just eliminate the problem) (ii) we can ADD BACK a "Nightly" column with RED/GREEN indicators to see what components are building nightly.
    • We will have to create PHP functions that are the equivalent of the wiki templates used on this page
  • The current components page is linked from the left-hand menu. The two new pages are linked from the new downloads page (see below) when that page is ready.

New Downloads Page

Here is the basic content of the new download page:

Higgins 1.0

  • table as below

Higgins 1.1

  • demo VirtualBox Linux image of a selector, and IdP, and some RP (and all source code) [ideally this would be updated every milestone]
  • 1.1M7 Table: Solutions
    • Section: Higgins Selector
      • Row: Selector Mac-AIR PSF <auto-built-download-page> MAN-BLD-LED INT-LED MAN-REG-TEST-LED <owner>
      • Row: Selector Win-AIR PSF <auto-built-download-page> MAN-BLD-LED INT-LED MAN-REG-TEST-LED <owner>
    • Section: Identity Services
      • Row: etc.
    • Section: Attribute Services
      • Row: etc.
  • Components 1.0 - link to a .php page (not a wiki page): only components that are part of one of the above solutions (not old 1.0 components)


Where:

  • PSF - a link to a PSF with every eclipse project needed to build and run the solution
  • MAN-BLD-LED - a RED/GRN LED that indicates if this solution can be manually built from scratch from instructions on the wiki page for this solution (using the PSF)
  • MAN-REG-TEST-LED - pass/fail LED on manual regression test (listed on solutions wiki page)
  • INT-LED - is this solution internationalized

Solutions 1.1

This section is a list of tasks to improve these solutions: Solutions 1.1 being planned for Higgins 1.1

Higgins Client

Cross-cutting issues (common to all Higgins client solutions):

New card types:

Client Solutions:

  • GTK and Cocoa Selector 1.1 - need to split and rename this wiki page according to the above, and update architecture diagrams with new HSS, new Synchronizing Card Store, etc. HIGH (Andy has done the actual refactoring, need to update the wiki doc) - [BUGZILLA#?]
  • AIR Client and Server 1.1 - get Parity to check in all code updates (e.g. new AIR ICM with skinnable "Higgins" UI branding (like what Andy did)) [BUGZILLA#?]
  • RCP - decide if Tie Li will update this for 1.1 [BUGZILLA#?]

Experimental New Client Solution:

  • iPhone Selector - I-Card Manager (standalone app) and I-Card Selector (MobileSafari plugin) for the iPhone


Solutions Pages

  • Revise all selector "so called" solutions wiki pages to indeed be solutions: meaning that they describe ALL of the components required to work. [This means that the solutions wiki pages for all but the "AIR client and server" need to be updated to add mention of HSS, HBX, and [in some cases] Higgins Server components or component sets] - HIGH [NEW]

Identity Web Services Solutions

Identity Provider web services:

  • STS IdP - WS-Trust Identity Provider (webapp and web service)
    • Get it to support WS-Trust 1.3 and SOAP 1.2 - [BUGZILLA#?]
  • SAML2 IdP - SAML2 Identity Provider (webapp and web service)
    • DONE: nothing to do

Relying Party website or service:

Other web app/services

  • Higgins Web Selector - Web proxy "client" for Higgins Server. Speaks OpenID with AX.
    • DONE: nothing to do

Identity Attribute Service Solutions

This solution is currently a local java component. The plan for Higgins 1.1 is to add an XDI web service binding and thereby create the "IdAS Server" that can act as an extensible gateway to existing data sources.

  • IdAS Solution - Identity Attribute Service uses Context Provider plugins to adapt existing data sources to the Context Data Model.

Other

  • XDI4j - General purpose library for XDI (see the Wikipedia page on XDI)

Components

IdAS-related components

  • 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

Higgins Browser Extension Component

Besides making sure that all H1.1 Selector solutions use the same HBXes, we also need to add support for:

  • un/pw login - HIGH
  • Microsoft's new CardTile option - HIGH
  • Work with Axel to integrate his new XRD discovery code - HIGH
  • Merge IDIB code (if possible), else recode in HBX - priority -- depends on what we want to show at RSA 2009 interop

Experimental:

Higgins Selector Switch Component

  • Versions for
    • Windows
    • Linux
    • MacOSX - HIGH
  • Merge connectors into the HSS - HIGH - [Jeesmon]
  • Windows selector connector for CardSpace and AIR - DONE
  • DigitalMe selector connectors (need MacOSX, Windows and Linux) - HIGH [Andy]


Infrastructure

Split Dependencies

  • Breaking every jar into its own Eclipse project (relationship to Orbit) (Mary to ask for volunteer on the list.)

Internationalization

  • Internationalization of certain CPs - done
  • Evaluate how could internationalization the clients so that can outsource creating localized versions.

Components Page

  • Comb through Components page and correct all missing wiki pages, etc.
    • Improve Components page by showing
      • Make it easy to see which component is used in 1.0, 1.1 or both - [DONE]
      • Make it easy to see which components are building properly in the nightly build

Galileo

  • Galileo - need to create a prioritized list of "to do"s even though we will not be part of Galileo so that we'll be in better shape for next year

Back to the top