Changes between Version 4 and Version 5 of T12_Security/OMII-UK/20080417
- Timestamp:
- 17/04/08 17:00:09 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
T12_Security/OMII-UK/20080417
v4 v5 7 7 * Security is now deployed at partner sites: NEODAAS (Plymouth) and NOCS (Southampton). Single Sign On and access to secured data has been demonstrated for PML and NOCSs users to BADC data. Problems: partner sites have limited resources for ongoing deployment work now that NDG2 is finished. More work is needed to get datasets secured and served through the NDG Browse interface. TODO: update BODC deployment for NDG Browse and security 8 8 * The Single Sign On and Gatekeeper (#963) interfaces for NDG Browse have been separated from the Browse code stack and made standalone within the NDG Security package. 9 * A client interface has been written for the existing BADC data browser for NDG Security to enable NDG partners to access data through this mechanism.9 * An NDG Security client interface has been written for the ''existing'' BADC data browser to enable NDG partners to access data through this mechanism. This ''supplements'' the NDG Browse (http://ndgbeta.badc.rl.ac.uk) and discovery (http://ndg.nerc.ac.uk/discovery) interfaces. The intention to this is to open up access for NDG partners to more BADC datasets. 10 10 1. Java Client Interface 11 11 * Some progress has been made with Python WS-Security - WSS4J interface. Signature verification is working but WSS4J certificate chain validation fails. Bryan Carpenter has provided support with this. There appears to be a bug with the WSS4J code.