Notes from Monday, October 26th, 2009 OpenPTK Owners Meeting

Attendees:

• Scott Fehrman
• Derrick Harcey
• Terry Sigle

PLANNED AGENDA:

1. Version 2 development update
2. Authentication and Authorization update and design discussion
3. Refactoring Strategy for client, common, and server packaging
4. Open Issues and priorities status discussion for 2.0
5. Version 2 release documentation / features page

MEETING NOTES:

Update on V2 development progress

Scott:
Porting of the tag library to use the client API has been completed
Tag library test porting completed
UML updated
Portlets updated

Misc. refactoring.
Client API Authentication calls for client and user information.
Added Phase 3 to Forgotten Password for change of the password.

Derrick:
User Interface refinement
Authentication 
Refactoring of Principals and addition of BasicCredentials object for authentication.
/login and /login servlets added
out of band implementation of login and logout completed.
filter extended to handle Global default authenticator design and implementation completed.

Not Enforced design is in progress.

Authorization

Design discussions has started and work in in progress.

Terry:

CLI is now using the client API, but not using the authentication.

Planned work to complete: add anonymous interaction with the CLI, allow a user to login to obtain a session with more privleges.

Authentication and Authorization update and design discussion

2.0 Design Authentication Framework

The authentication design is implemented. A session type of internal was added for scenarios where anonymous access is turned off in the configuration.

Not Enforced design (which is related to authorization) is in progress.

2.0 Design Authorization Framework

Authorization is in process. There was a discussion of the current state of the design.

The design terminology was discussed and the terminology used in XACML was considered.

The components which will use the authorization were discussed and the functions needed are important to address.

Brainstorming of the terminology was done.

Refactoring Strategy for client, common, and server packaging

Current proposed strategy:
[2.0 Package]

Scott discussed the current proposed strategy as documented on this page.

Scott will add a Service table and add additional diagrams for build and deploy dependencies

Terry will open an issue for 2.1 on a designing a solution to maintain the build number in the build process and potentially perform version depencency checks of the openptk.xml file against the version of the server which is being used.

Next Steps:

1) Scott will update the document to show the complete end state proposed, and send an announcement.
2) Derrick and Terry will review and validate all details of the information on the page
3) Add a test plan to the wiki page for validation after the refactoring is completed.
4) Once the documentation is ready for a final review, another Owners meeting will be scheduled for final review and approval
5) Tasks and ownership of the refactoring work will be assigned and we will each assist with the refactoring work.

Open Issues and priorities status discussion for 2.0

A new version 2.1 will be added to the system. All issues which are not planned to be released in 2.0 will be change to version 2.1 in the issue tracking system.

Open Issue: Once the refacforing design is completed, we will create new components and sub-components to match the version 2 design.

Version 2 release documentation / features page

The full feature list for 2.0 is not currently documented in a single place in a simple and clear list. The issue tracker can generate the list of features. The What's New page referenced below should be used to list the high level features.

Docs 2.0 What's New

Action item, (all owners) agree to review the enhancements and features for 2.0 an add any additional items which need to be added. Also any items which are not planned for version 2.0 also will be moved to v2.1.

The complete documentation plan will be discussed on the next Owners Meeting since development is still in process.