Reference‎ > ‎Meeting Minutes‎ > ‎

Minutes: 2009-04-14

Notes from Tuesday, April 14, 2009 9:33pm CST OpenPTK Status Call

This is a Owners meeting.

Attendees:

  • Scott Fehrman
  • Derrick Harcey
  • Terry Sigle

PLANNED AGENDA:

  • Status of OpenPTK 1.x
  • Feature List for OpenPTK 2.0
  • Open Issues
  • Development Activities / Process
    • Consideration of Forgotten Password Services as OpenPTK Feature

MEETING NOTES:

Status of OpenPTK 1.x

  • Everyone agress that OpenPTK 1.x (including 1.1 and 1.2) is feature complete. 
  • No more changes except for emergency fixes.
  • Current development is in the Trunk (future OpenPTK 2.0)

Feature List for 2.0

  • Core Architecture enhancements
    • Encryption of proxy credentials (implemented)
    • Handling of null values (95% implemented)
    • Handling of functions and chaining (implemented)
  • Security design of v2
    • Phase 1 of AuthN (design)
    • Phase 1 of AuthZ (design)
  • Framework
    • Attribute Function ReDesign (implemented)
    • Definition Enhancement (implemented)
    • Function::Argument Change (implemented)
    • Attribute Error/State/Status (50% implemented)
    • Rename Context objects (design)
    • Resolve Missing Attributes Scenarios (LDAP like -vs- SQL like) (50% implemented)
  • Service
    • SPML2 Support (implemented)
    • JNDI/JDBC Password Support (implemented)
  • Consumer
    • Phase 1 - RESTful Web Service (design)
  • Application
    • CLI - Output Options (LDIF, Table, CSV) (design)
    • JavaFX (RESTful Consumer) (design)
    • provlet (RESTful Consumer) (design)
    • Enhance Portlets to include Setting Question/Answer (design)

Feature List for 2.0+

  • Discuss server packaging of V2
  • Discuss repository concept of v2
  • Framework Services (Parity across services)
    • ENABLE and DISABLE service Operations
    • Forgotten Password service Operation
  • Framework
    • Person Relationships
    • Function Processing
    • Message Catalog - Error Messages & Apps
    • Multiple-Service Contexts
  • Service
    • JMS
  • Application
    • Consider RESTful interface for all apps
    • Role Management

Open Issues

  • Decided to individually scan open issues

Development Activities / Process

Authentication Design

  • After a lot of discussion, it was determined that we do need to look at a 1st version of sessions.
  • Scott will create some initial designs/pseudo code on wiki for immediate collaboration.
  • Initially, thought is to include all the new session, authentication, credential and session implemenations as a part of org.openptk.provision packages.

Consideration of Forgotten Password Services as OpenPTK Feature

  • Derrick to take this on as a item to create an initial design.

Next meeting topics:

  • Session Review
  • Authentication Review
  • RESTful Review
  • RESTful Client Prototypes Review
  • Review High Priority Issues
  • Scheduling Release of 2.0

Meeting ended: @ 12:46am, Tax Day, 4/15/09