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.
Difference between revisions of "Jan 29-31 Provo F2F Agenda"
(→General) |
(→Preliminary Agenda) |
||
| Line 40: | Line 40: | ||
# David Primmer - Google (for session on STS IdP + SAML IdP refactoring) | # David Primmer - Google (for session on STS IdP + SAML IdP refactoring) | ||
| − | == | + | == Tuesday == |
| − | + | ||
| − | * [[ | + | === [Paul, Mary, Dale] 9:00-9:20 Welcome, Introductions, Logistics === |
| − | * Review of | + | * Introductions |
| − | * | + | * Eclipse ground rules |
| + | * Logistics | ||
| + | |||
| + | === IdAS & IGF Design [Jim and Phil] === | ||
| + | * Call in session?? | ||
| + | * Presentation of IGF Requirements | ||
| + | |||
| + | === [Paul & Jim] Higgins Data Model === | ||
| + | * See [[Higgins Data Model]] | ||
| + | * HOWL & IdAS | ||
| + | ** [Paul] Review of proposed changes to higgins.owl | ||
| + | ** Quick look at OWL 1.1 | ||
| + | ** Relax to OWL-Full (withdraw decidability requirement) | ||
| + | ** Jim's 4/5 open issues '''need to enumerate them here''' | ||
| + | |||
| + | === The Future of the Configuration Component === | ||
* Configuration component: need two versions of Configuration.common (one for plugin-based configurations and one for jar-based configurations) | * Configuration component: need two versions of Configuration.common (one for plugin-based configurations and one for jar-based configurations) | ||
| − | * | + | * Writeable configurations? |
| − | * | + | * Configuration UI? |
| − | * | + | |
| − | + | ||
| − | * | + | |
| − | + | ||
| + | == Wednesday == | ||
| + | |||
| + | === [2hrs] [Mike] STS IdP Solution in Depth === | ||
| + | * Similar to New York F2F sesion, but shorter | ||
| + | * (Weds or Thurs please) | ||
| + | * STS Work items: | ||
** STS token service still bypasses IdAS to access/update attributes | ** STS token service still bypasses IdAS to access/update attributes | ||
** Sample STS should cut over to using XMLFile Context Provider | ** Sample STS should cut over to using XMLFile Context Provider | ||
** Use of "informationCard generator" in STS's profile service? | ** 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) | ** Currently the STS MEX endpoint only advertises support for transport-level security (using UN token or self-seigned SAML token) | ||
| + | |||
| + | === [Paul] Card-based OATH === | ||
| + | * Support for OATH in the world of Higgins | ||
| + | * Oauth uses redirects all over the place and asks the person to sign in using un/pw at the service provider. There must be a better user experience. | ||
| + | * How about O-cards? User experience: | ||
| + | ** User gets an O-card from Service Provider (e.g. Google Calendar) | ||
| + | ** User fires up Oauth Consumer that wants Google Calendar data stream | ||
| + | ** Selector appears with Google Calendar card displayed | ||
| + | ** Selector UI asks to approve grant of rights | ||
| + | ** User clicks "Approve" button | ||
| + | ** Done. [No redirects, no un/pw entry at SP, etc.] | ||
| + | |||
| + | === [Mike] Merging SAML2 IdP into STS framework === | ||
| + | * Pre-merge refactoring | ||
| + | ** Should we rename low level reusable sts.* components -> htp.* (Higgins Token Processing) | ||
| + | * Task planning | ||
| + | * Resources | ||
| + | |||
| + | |||
| + | === 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 | ||
| + | |||
| + | == Thursday (ends at noon) == | ||
| + | |||
| + | == 1.0 and 1.1 and... Plan == | ||
| + | * Review of outstanding bugzilla bugs (known bugs in 1.0) | ||
| + | * Branch proposal: | ||
| + | ** Create branches (as we do now) for stable builds | ||
| + | ** Just keep marching towards 1.1, 1.2, 1.3 etc. | ||
| + | |||
| + | === [Paul] Introduction to COIN === | ||
| + | * http://openidentitynetwork.org | ||
| + | * What will COIN do? | ||
| + | * Status of incorporation/launch | ||
| + | * Marketing plan for 2008 | ||
| + | * Operating plan for 2008 | ||
| + | |||
| + | === [Paul] Review and discussion of alternative to Microsoft's i-card logo === | ||
| + | * Why we can't live with the current one | ||
| + | * Road forward | ||
| + | |||
| + | === [Paul, Mary] Marketing & Outreach === | ||
| + | * [Paul] New higgins-project.org website | ||
| + | * [Mary] Press release plan: coordination with Eclipse Foundation | ||
| + | * Outreach to independent OSS developers | ||
| + | ** What should we be doing? Should we have an plan? | ||
| + | ** What example CPs would get folks excited? A Twitter CP? | ||
| + | * Outreach to other related efforts | ||
| + | ** Dataportability.org - What more should we be doing | ||
| + | ** Semantic Web crowd | ||
| + | ** ...other groups | ||
| + | |||
| + | == Fodder == | ||
| + | Fodder: | ||
| + | * [[Beyond Higgins 1.0]] <-- lots of topics for discussion here | ||
| + | |||
* 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) | * 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 | * Planning for Higgins 1.1M1 | ||
| Line 67: | Line 162: | ||
*** we're currently passing objects around that are hard to serialize | *** we're currently passing objects around that are hard to serialize | ||
*** use JSON | *** use JSON | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* IdAS data model discussion | * IdAS data model discussion | ||
* IdAS extensible APIs | * IdAS extensible APIs | ||
Revision as of 00:09, 24 January 2008
Contents
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)
Tuesday
[Paul, Mary, Dale] 9:00-9:20 Welcome, Introductions, Logistics
- Introductions
- Eclipse ground rules
- Logistics
IdAS & IGF Design [Jim and Phil]
- Call in session??
- Presentation of IGF Requirements
[Paul & Jim] Higgins Data Model
- See Higgins Data Model
- HOWL & IdAS
- [Paul] Review of proposed changes to higgins.owl
- Quick look at OWL 1.1
- Relax to OWL-Full (withdraw decidability requirement)
- Jim's 4/5 open issues need to enumerate them here
The Future of the Configuration Component
- Configuration component: need two versions of Configuration.common (one for plugin-based configurations and one for jar-based configurations)
- Writeable configurations?
- Configuration UI?
Wednesday
[2hrs] [Mike] STS IdP Solution in Depth
- Similar to New York F2F sesion, but shorter
- (Weds or Thurs please)
- STS Work items:
- 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)
[Paul] Card-based OATH
- Support for OATH in the world of Higgins
- Oauth uses redirects all over the place and asks the person to sign in using un/pw at the service provider. There must be a better user experience.
- How about O-cards? User experience:
- User gets an O-card from Service Provider (e.g. Google Calendar)
- User fires up Oauth Consumer that wants Google Calendar data stream
- Selector appears with Google Calendar card displayed
- Selector UI asks to approve grant of rights
- User clicks "Approve" button
- Done. [No redirects, no un/pw entry at SP, etc.]
[Mike] Merging SAML2 IdP into STS framework
- Pre-merge refactoring
- Should we rename low level reusable sts.* components -> htp.* (Higgins Token Processing)
- Task planning
- Resources
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
Thursday (ends at noon)
1.0 and 1.1 and... Plan
- Review of outstanding bugzilla bugs (known bugs in 1.0)
- Branch proposal:
- Create branches (as we do now) for stable builds
- Just keep marching towards 1.1, 1.2, 1.3 etc.
[Paul] Introduction to COIN
- http://openidentitynetwork.org
- What will COIN do?
- Status of incorporation/launch
- Marketing plan for 2008
- Operating plan for 2008
[Paul] Review and discussion of alternative to Microsoft's i-card logo
- Why we can't live with the current one
- Road forward
[Paul, Mary] Marketing & Outreach
- [Paul] New higgins-project.org website
- [Mary] Press release plan: coordination with Eclipse Foundation
- Outreach to independent OSS developers
- What should we be doing? Should we have an plan?
- What example CPs would get folks excited? A Twitter CP?
- Outreach to other related efforts
- Dataportability.org - What more should we be doing
- Semantic Web crowd
- ...other groups
Fodder
Fodder:
- Beyond Higgins 1.0 <-- lots of topics for discussion here
- 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
- 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.