Hi James, et al:
Ethan Davis wrote:
Currently, the TDS doesn't do any authentication/authorization for data access. But it is in the plans. John would have a better idea of the time line for that than I. (Actually, I may be overstating this. You may be able to set it up to do authentication/authorization for data access but only on a server-wide level, or at least the user would have to do all the mucking around with Tomcat. Sorry for the flip-flopping. Now that I think about it more it turns out I'm just not that sure. John would know better and should be around on Monday.)
The TDS does do authentication/authorization (a la Tomcat) for server configuration and such. If you want more details, see the "Remote Management" and "Security" links from our TDS docs page http://motherlode.ucar.edu:8080/thredds/docs/.
James Gallagher wrote:
I'm hacking together a document of 'Best Practices' about DAP servers and I was wondering what sort of username/password protection GDS, FDS and TDS supply? I sort of know what a servlet engine like Tomcat 5.5 can do (although I'm nowhere near an expert on it).
There's sort of a short time line on this; I need to get my text to Dan soon but I should have a chance to hack in some changes until Tuesday.
Thanks, James -- James Gallagher jgallagher at opendap.org OPeNDAP, Inc 406.723.8663
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.