The following list of tasks were discussed as either in process or in planning stages for version 2. The priority is not a measure of the importance of the feature, just the order in which features are expected to be completed as there are many dependencies.

Issue Tracker

Warning

All issues are being managed in the issue tracker on openptk.dev.java.net

All Tasks should be entered into the Issue Tracker. The following Priority levels shall be used for features/enhancements to OpenPTK 2.0:

Priority	Name	Description
P3	High	Feature / Enhancement is the critical path for other development
P4	Medium	Reguired for release, not in critical path
P5	Low	Nice to have for release

P1 and P2 Priority Level are used for Issues that effect existing features / capabilities that do not function properly.

Priority	Issue	Task	Owner	Status
High	90	RESTful Client project that supports RESTful / Authen	Scott	Design phase
High		Authentication on server with a servlet filter design. Functionality in place. updates for client framework are needed.	Derrick	TBD
Medium		Enhance Update Operation. Currently the entire entry is sent to the Framework. The Client / Representation needs to be update to support only those attributes that have changed.		TBD
Medium		CLI/Console, re-design to use RESTful Client project	Terry	tbd
Medium		Taglib, re-design to use RESTful Client project	Terry	tbd
Medium		Portlets, re-design to use RESTful Client project	Terry	tbd
Medium		Server Anon: Registration and forgotten password Interface	Derrick	in process
Medium		Server Whitepages Interface	Derrick	in process
Medium		Server Self Service Interface	Derrick	in process
Medium		Server Admin Interface - show contexts, config, logs	Derrick	in process
Medium		Server Stylesheets and branding	Derrick	in process
Medium		Server AJAX and UI Widgets / javascript library design	Derrick	in process
Medium		Engine Instrumentation. Need to update as new Objects / Resources are added.	Scott	Ongoing
Medium		Strip encrypted fields from RESTful results (password, etc.) - related to authorization	Scott	TBD
Medium		Advanced search to specify attribute(s) and operator to search against	Scott	TBD
Medium		Filter should not hard code and authenticator, should use client properties (authenticator = _engine.getAuthenticator("Employees-IdPass-LDAP") Requires client design to be complete.	Derrick	TBD
Medium		Client details should be exposed without requiring access to the engine resource. For example the context to use for a given client and the search quantity and min chars and search properties, etc. This might require a client resource to be exposed for the meta data to be exposed in a bootstrap process	Scott / Derrick	TBD
Low		Create "worker thread" for Engine that scans for expired Sessions	Scott	tbd
Low		Refactor Filter and authenticators to be JAAS compliant	Derrick	tbd
Low		Enahance `ptkadmin` to generate random string, used as a shared secret	Scott	tbd
Low		Default Response: Handle only requested attributes, rather than all attributes in the attrgroup	Scott	TBD
Low		html converter formatting / stylesheet support		TBD
Low		Server Authorization, course grained done via Session Type (ANON, USER, SYSTEM)		fined grained TBD
Low		Default Search extensions: consider internal OR implementation		TBD
Low		New Service: Identity Connectors	Tuhin	In Process
Low		New Service: Message Queue		TBD
Low		New Service: LDAP using UnboundID SDK		TBD
Low		SPML v1 approval processing / launch workflow		TBD
Low		Email Notifications integration		TBD
Low		Server Side Search RESTful suggest function	Derrick	TBD
Priority	Issue	Task	Owner	Status
High	89	Startup, handling of Contexts that can not be used. Context class validation on startup. Disabled Contexts should not try to initialize. If there is initialization failure, make it DISABLED. Need to re-design XMLConfig. Update URI for `context` and `engine`	Scott	fixed
High		~~Model - Context and Model/Relationship/Views~~	Scott	Done
High		~~Server Session ID implementation~~	Scott	Done
High		~~Server Side search results caching and pagination~~	Scott	Done
High		~~Intitial Implementation of Server Login Interface~~	Derrick	Done
High		~~Implement Athenticator to support JNDI Id/Pass and Token~~	Scott	Done
Medium	91	~~Enhance `Relationship` to support use of "external" `Context`. Needed to leverage location data that's in another `Context` for phonebook application~~	Scott	fixed
Medium		~~JDBC Service update to use AND and OR Operators if possible~~	Terry	Done
Medium	30	~~RESTful Create, Update, Delete~~	Scott	Done
Medium	88	~~Properly handle integers and booleans in converters~~	Scott	Done
Medium	86	~~Add Server configuration to the openptk.xml and xsd~~	Derrick	Done
Low	87	~~RESTful password management~~	Scott	Done

Developer Task List

Issue Tracker

Labels