Not Enforced design is in progress.
Design discussions has started and work in in progress.
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.
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.
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.
Current proposed strategy:
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.
1) Scott will update the document to show the complete end state proposed, and send an announcement.
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.
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.
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.