Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Jan 29-31 Provo F2F Agenda
General
Higgins face-to-face meeting in Provo, Utah, January 29-31, 2008.
Location Novell's office. 1800 South Novell Place, Provo, UT 84606, (801) 861-7000
The event will start Tuesday at 9:00AM and end Thursday at noon.
For early-comers and late-leavers, we're planning one or more ski days. See the ski poll
Hotel: Several of us are staying at the Marriott Conference Center in Provo (Map). There are also a few hotels within walking distance (may have to deal with snow though)
Weather Dress warm. It may be cold.
Getting there: Most people fly into the SLC airport and drive to Provo. Here are directions from SLC International Airport to Novell.
Expected Attendees
- Dale Olds - Novell
- Jim Sermersheim - Novell
- Mary Ruddy - SocialPhysics/Parity
- Paul Trevithick - SocialPhysics/Parity
- Tony Nadalin - Bandit
- Tom Doman - Novell
- Daniel Sanders - Novell
- Phil Hunt - Oracle
- Drummond Reed - Cordance/Parity
- Andy Hodgkinson - Novell
- Duane Buss
- Michael McIntosh - IBM
- Markus Sabadello - Parity
- Carl Binding - IBM
- Uppili Srinivasan - Oracle
- Bruce Rich - IBM
- George Stanchev - Serena
- Anthony Bussani - IBM
Attending by Phone (watch this space for conf #):
- Brian Carroll - Serena
- Paula Austel - IBM
- David Primmer - Google (for session on STS IdP + SAML IdP refactoring)
Preliminary Agenda
Fodder:
- Beyond Higgins 1.0 <-- lots of topics for discussion here
- Review of outstanding bugzilla bugs (known bugs in 1.0)
- Higgins IdAS and IGF design - call in session?
- Configuration component: need two versions of Configuration.common (one for plugin-based configurations and one for jar-based configurations)
- Drill down on STS - Mike M. (Weds or Thurs please)
- Merging SAML2 IdP into STS framework
- Naming
- rename low level reusable sts.* components -> htp.* (Higgins Token Processing)
- use the term "STS" or "SAML IdP" for deployment configurations
- Naming
- Support for OATH in STS framework
- STS token service still bypasses IdAS to access/update attributes
- Sample STS should cut over to using XMLFile Context Provider
- Use of "informationCard generator" in STS's profile service?
- Currently the STS MEX endpoint only advertises support for transport-level security (using UN token or self-seigned SAML token)
- Merging SAML2 IdP into STS framework
- Discuss the development of a "portable ledger" format that would allow import/export of this ledger so that card history could be maintained (at least within Higgins selectors)
- Planning for Higgins 1.1M1
- Aligning the 1.1 road map with the RSA interop
- Configuration component
- support "writing" not just reading
- better support for passwords in the file
- make it possible to do "round tripping" somehow (MikeM)
- central configuration service?
- problems: how to transfer stuff from file system (e.g. keystore) to the service?
- we're currently passing objects around that are hard to serialize
- use JSON
- Novell open source IdP presentation (Weds or Thurs please)
- This uses the Higgins STS and IdAS components. Presentation will include the following:
- High level architectural overview of IdP and how Higgins STS and IdAS are used.
- Demonstration.
- Download the IdP tarball.
- Build it.
- Deploy to server that has Tomcat installed.
- Configure using web based admin.
- Miscellaneous configuration.
- Configuration of attributes that can be stored.
- Configuration of information card templates.
- Configuration of Java keystore
- Configuration of IdAS context provider.
- Look at the XML configuration files that are generated by admin.
- Customizing how the IdP will look and feel.
- Create user account
- Manage user account, including change password
- Issue information card using a card template
- Use information card
- Review and discussion of new i-card logo
- IdAS data model discussion
- IdAS extensible APIs
- Discussion of how we will publicize Higgins 1.0.
- Communities we need to target, resources
- Website efforts, etc.