[Go-essp-tech] Example of configuring a datanode to serve CMIP3-DRS

[ag.stephens at stfc.ac.uk]

Hi Martin,

Just to note that myself and Mick Carter at the Met Office are looking into what security re-configurations might be required to allow access to the MyProxy certificate service. All info will be fed back to Phil so that we can document it for other data users that might hit firewall problems.

Cheers,

Ag


-----Original Message-----
From: go-essp-tech-bounces at ucar.edu on behalf of stephen.pascoe at stfc.ac.uk
Sent: Tue 6/29/2010 15:42
To: go-essp-tech at ucar.edu; is-enes-sa2-jra4 at lists.enes.org
Subject: [Go-essp-tech] Example of configuring a datanode to serve CMIP3-DRS
 
To illustrate how the ESG datanode can be configured to serve data for
CMIP5 we have deployed a datanode containing a subset of CMIP3 in the
Data Reference Syntax. Some key features of this deployment are:

*	The underlying directory structure is based on the Data
Reference Syntax.
*	Datasets published at the realm level.
*	The token-based security filter is replaced by the
OpenidRelyingParty security filter.

Further notes can be found at
http://proj.badc.rl.ac.uk/go-essp/wiki/CMIP3_Datanode
 
This test deployment should be of interest to anyone wanting to know how
DRS identifiers could be exposed in THREDDS catalogues and the TDS HTML
interface.  You can also try downloading files with OpenID
authentication or via wget with SSL-client certificate authentication.
See the link above for details.
 
Cheers,
Stephen.
 
 
---
Stephen Pascoe  +44 (0)1235 445980
British Atmospheric Data Centre
Rutherford Appleton Laboratory
 

-- 
Scanned by iCritical.


-- 
Scanned by iCritical.