Release Notes

The purpose of this section is to provide a description of a Security Service release including any impact that the new or modified capabilities will have on the Discipline Nodes or the PDS user community. If viewing the web-based version of this document, a somewhat itemized list of changes for each release can be found on the Release Changes page.

Release 0.3.0

This release of the Security Service is a component of the integrated releases 1.1.0 and 1.2.0 of the PDS 2010 System. This release is intended as a prototype release in support of the assessment of the PDS4 standards and the system components to date. The new or modified capabilities for this release are as follows:

• Simplified the deployed solution by utilizing a single directory service to satisfy the requirements.

The liens for this release are as follows:

• Need to define a procedure for synching this list with the personnel entries in the Registry Service.
• Need to develop a solution for obtaining and passing cookies.

Release 0.2.0

This release of the Security Service is a component of the integrated release 1.0.0 of the PDS 2010 System. This release is intended as a prototype release in support of the assessment of the PDS4 standards. The new or modified capabilities for this release are as follows:

• Added support for controlling access to HTTP PUT and DELETE methods.
• Added support for controlling access based on group membership.

The liens for this release are as follows:

• Need to resolve an issue defining policy for multiple HTTP methods on the same URL.
• Need to clean up the user list and define a procedure for synching this list with the personnel entries in the Registry Service.

Release 0.1.0

This release of the Security Service is a component of the integrated release 0.1.0 of the PDS 2010 System. This release is intended as a prototype release in support of the demonstration at the Management Council Face-to-Face meeting in August 2010. This initial release of the service provides the capability to secure specific URLs for the Registry Service and force requests to those secure URLs to require authentication.