NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
On Aug 27, 2009, at 5:04 PM, John Caron wrote:
Pauline Mak wrote:For TDS, you can use standard Tomcat authentication, see authentication section of this:Hi all,Is there any documentation on OPeNDAP/G, or THREDDS with X509 documentation? We're interested in using authentication (and naturally, authorisation) for some of our datasets. I would like to see if I can do a test setup over here, but I can't seem to find any documentation on doing this... Interestingly, does OPeNDAP client libraries already support this?Thanks! -Pauline.http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.0/reference/index.htmlIm guessing same for Hyrax. OPeNDAP client libraries should support this, as its based on standard HTTP mechanism.
Yes, as both Patrick and John suggest, Hyrax depends on Tomcat for security. Here's the documentation on that: http://docs.opendap.org/index.php/Hyrax_-_OLFS_Configuration#Authentication_.26_Authorization
The C++ library and new C client-side library (and thus new netCDF DAP access) support cookies which is, I believe, what is required for single sign on systems, although more might be required on the server side.
James
_______________________________________________ thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
-- James Gallagher jgallagher at opendap.org 406.723.8663
thredds archives: