Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Jan 29-31 Provo F2F Agenda"

Line 4: Line 4:
  
 
The event will start Tuesday at 9:00AM and end Thursday at noon.
 
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 [http://www.doodle.ch/participation.html?pollId=vmwkdbedcypcrci3 ski poll]
  
 
Hotel: Several of us are staying at the Marriott Conference Center in Provo ([http://maps.google.com/maps?f=d&hl=en&geocode=&time=&date=&ttype=&saddr=101+West+100+North,+Provo,+UT&daddr=1860+South+100+E,+Provo,+UT&sll=40.215587,-111.652679&sspn=0.023497,0.057335&ie=UTF8&ll=40.221705,-111.658295&spn=0.02683,0.00447&om=1&source=embed Map]).
 
Hotel: Several of us are staying at the Marriott Conference Center in Provo ([http://maps.google.com/maps?f=d&hl=en&geocode=&time=&date=&ttype=&saddr=101+West+100+North,+Provo,+UT&daddr=1860+South+100+E,+Provo,+UT&sll=40.215587,-111.652679&sspn=0.023497,0.057335&ie=UTF8&ll=40.221705,-111.658295&spn=0.02683,0.00447&om=1&source=embed Map]).
Line 33: Line 35:
 
* Higgins IdAS and IGF design - call in session?  
 
* 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)
 
* 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.
+
* Drill down on STS - Mike M. (Weds or Thurs please)
 
** Merging SAML2 IdP into STS framework
 
** Merging SAML2 IdP into STS framework
 
*** Naming
 
*** Naming
 
**** rename low level reusable sts.* components -> htp.* (Higgins Token Processing)  
 
**** rename low level reusable sts.* components -> htp.* (Higgins Token Processing)  
 
**** use the term "STS" or "SAML IdP" for deployment configurations
 
**** use the term "STS" or "SAML IdP" for deployment configurations
** Support for OATH in STS framework
+
** Support for OATH in STS framework  
 
** 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
Line 53: Line 55:
 
*** 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
* Presentation and demo of a Novell open source IdP that uses Higgins STS and IdAS components.  Presentation will include the following:
+
* 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.
 
** High level architectural overview of IdP and how Higgins STS and IdAS are used.
 
** Demonstration.
 
** Demonstration.
Line 72: Line 75:
 
*** Use information card
 
*** Use information card
 
* Review and discussion of new i-card logo
 
* Review and discussion of new i-card logo
 +
* IdAS data model discussion
 +
* IdAS extensible APIs
  
 
== Links ==
 
== Links ==
 
* [http://eclipse.org/higgins Higgins Home]
 
* [http://eclipse.org/higgins Higgins Home]

Revision as of 22:38, 15 January 2008

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) The markers are off. From left to right,

  • The La Quinta is across the street (west) and has a visible swimming pool.
  • The Fairfield has a blue roof
  • The Hampton is next to (east) of the Fairfield
  • The Sleep Inn is next to (northeast) of the Hampton

Weather Dress warm. It may be cold.

Expected Attendees:

  1. Dale Olds - Novell
  2. Jim Sermersheim - Novell
  3. Mary Ruddy - SocialPhysics/Parity
  4. Paul Trevithick - SocialPhysics/Parity
  5. Tony Nadalin - IBM
  6. Tom Doman - Novell
  7. Daniel Sanders - Novell
  8. Phil Hunt - Oracle
  9. Drummond Reed - Cordance/Parity

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
    • 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)
  • 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
  • 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

Links

Back to the top