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"

(Higgins Browser Extension Component)
(New Card Types)
Line 114: Line 114:
  
 
== New Card Types ==
 
== New Card Types ==
* [[Password Card]] - (see [[PWMgr and Password Cards]]) - '''HIGH'''
+
* [[Password Card]] - (see [[Password Cards]]) - '''HIGH'''
 
* [[R-Card]] - ''HIGH''
 
* [[R-Card]] - ''HIGH''
 
* OpenID - would be nice
 
* OpenID - would be nice

Revision as of 12:51, 4 March 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 updated and linked to.

Tentative Plan

  • June date - Shadow Eclipse Release train if possible <-- now looking very unlikely
  • 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.

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

Architectural consistency:

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 Renaming

Renaming these solutions:

  • Higgins Client for MacOSX (AIR) - includes Higgins Selector for MacOSX (AIR), HSS for MacOSX, HBX for Firefox
  • Higgins Client for MacOSX (Cocoa) - includes Higgins Selector for MacOSX (Cocoa), HSS for MacOSX, HBX for Firefox
  • Higgins Client for Windows (AIR) - includes Higgins Selector for Windows (AIR), HSS for Windows, HBX for Firefox
  • Higgins Client for Windows (GTK) - includes Higgins Selector for Windows (AIR), HSS for Windows, HBX for Firefox
  • Higgins Client for Linux (GTK) - includes Higgins Selector for Linux (GTK), HSS for Linux, HBX for Firefox

Renaming these client component sets to: HIGH

  • Selector for MacOSX (AIR)
  • Selector for MacOSX (Cocoa)
  • Selector for Windows (AIR)
  • Selector for Windows (GTK)
  • Selector for Windows (RCP)
  • Selector for Linux (GTK)
  • Higgins Selector Switch for Windows
  • Higgins Selector Switch for MacOSX
  • Higgins Selector Switch for Linux

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

  • 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

  • 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

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]

New Card Types

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

Back to the top