Attendees
* Brian Carroll - Serena
* Tom Carroll - Parity
* Mary Ruddy - Meristic
* Brian Walker - Parity
* Hank Mauldin – Cisco
* John Bradley
* Markus Sabadello - Parity
* George S - Serena
Logistics
Time: noon Eastern
Dial-in: 1-866-362-7064 / 89-2048#
Agenda
1. [Brian] 1.1M7 targeted for May 15
See [1]
Targeting mid-May for current update of solutions and wiki page
download re-organization. This date may move depending on progress
over coming weeks.
2. [Brian, Alexander, Andy] Selector Architecture Harmonization
See [3]
Currently working on finishing LICS. Will need to do some follow up
clarification as part of work transfer from Andy to Valery to clarify
some implementation details. Targeting late May to have next working
milestone of GTK on LICS and support m-card transactions as well.
The FC2 team is interested in using this solution.
3. [Paul/Brian] Website improvements next steps
Implement new downloads page structure [4]
New page for builds that can’t be build in Higgins [5]
No major updates to proposal - just need to focus on implementation.
Have been focused on RSA prep over much of the past week.
4. [Markus, Paul] CardSync Protocol proposal
See the latest outline here: http://wiki.eclipse.org/CardSync_Protocol
Want CardSynch to be indipendant on card store technology.
Remote card store on embedded device may have different use cases.
Would need to review this with Alexander to develop further.
·
5. [Andy] DigitalMe polishing for end user consumption
Will have to cover this at next meeting (after RSA) when Andy is
available.
6. [John] Extending the IMI to support the web proxy selector
There is question outside the i-card community if there is there a
demand for this? Do we need another redirect protocol? Would require a
non-trivial effort for the early stage of icard adoption. This would
be needed/useful for kiosk or iphone type i-card support.
Have had some discussion of different approaches in the IMI TC for
delivery of info cards - the different approaches could include:
Attribute exchange - but can't send signed tokens among other
limitations.
Multiprotocol SAML - convert from wsfed/saml token to straight saml
token. Would have some sizable code deployment,. Larger burden on RP's.
Tweak wsfed so the RP gets a realm identifier (look like OP
identifier). This would be the simplest from an RP perspective. wsfed
does not deal with object tags. Most of the work would be figuring how
to make this campatible to wsfed yet can be understood by RP.
Any of the above choices would required changes on the RP side.
7. IMI spec update [John] - target is to get updated spec out by June
timeframe. Currently in public review. OASIS votes will be key to
approve this and people will be reminded about this when it is time to
vote on this spec.
[1] http://wiki.eclipse.org/Higgins_1.1M7
[2] http://wiki.eclipse.org/Selector_Architecture_Harmonization
[3]
http://wiki.eclipse.org/Higgins_1.1_Plan#Infrastructure_.26_Cross-cutting_Improvements
[4] http://wiki.eclipse.org/Higgins_1.1_Plan#New_Downloads_Page
[5] http://www.higgins-solutions.org/
Brian Walker
[email protected]
VP of Engineering
Azigo
www.azigo.com
_______________________________________________
higgins-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/higgins-dev
