General
| Feature |
Description |
| Client - Server Validation |
Design a mechanism for how the Client can validate (authenticate the client, not the end user) itself to the Server |
| Server packaging |
Deliver the OpenPTK solution as a deploy-able service in a web container. Support for on-line configuration and management |
Download Bundles
|
Prepare the different download options for various OpenPTK bundles
|
| encryption of proxy credentials |
Storing client-side credentials for use
by the service should be encrypted. Will require general encryption
mechanism used by the Framework and Service |
| Error code/message facility |
Create a mechanism that would manage
error codes, levels, description, and action information. This facility
would be used by all Tiers. Developers will register new errors with the
facility and leverage an error handling API. All "hard coded" errors
will be removed from source files. |
| State Enumerations |
State Enumerations (in base package) are used by multiple packages. Declare which enumerations apply to a tier. |
Logging
|
Design and implement an OpenPTK Logging
service that will be the centralized logger for all log activities. It
should be instantiated based on the Logger settings from the openptk.xml
configuration.
|
| Logging Password Data: Authentication |
Various points in the login process are "logging" the user credentials (password) to a file. |
Maven Support
|
Document the steps necessary for a conversion to a Maven based project.
|
|
|
