Updated README and TODO files to reflect the current state of the
project.
This commit is contained in:
@@ -82,18 +82,13 @@ The auth_token client/service protocol allows for the authentication of the clie
|
||||
auth_token relies in the server authentication mechanisms of SSL to verify the identity
|
||||
of the ATS.
|
||||
|
||||
IMPLEMENTATION STRATEGY AND CURRENT STATUS
|
||||
CURRENT STATUS
|
||||
|
||||
auth_token is currently under development and is not ready to be used in production.
|
||||
The implementation strategy has been to first complete the framework with all of its
|
||||
modules, APIs, and packaging to allow application writters to start developing to it.
|
||||
Once this is done, then the implementation focus will switch to completing the plumbing.
|
||||
CASA-auth-token status is mostly code complete and has entered the testing phase. We will
|
||||
be making changes during this phase based on the feedback received.
|
||||
|
||||
As of this time, a lot of the framework has been completed and there are sample
|
||||
applications that can be utilized to exercise it. For a more complete picture of where
|
||||
we are, look at the various TODO lists present in the child folders.
|
||||
|
||||
The schedule for completing auth_token is agressive.
|
||||
The items whose implemetation is still pending are listed in the TODO files for the various
|
||||
components.
|
||||
|
||||
SECURITY CONSIDERATIONS
|
||||
|
||||
|
||||
Reference in New Issue
Block a user