Re: [Fwd: Re: opendap restricted access]

Thomas LOUBRIEU wrote:
Hi John,

I am not sure of the exact content of the CAS server but I think the redirect order is sent through a specific http error code (302). You can do "wget -S 'http://..."; in order to see what happens.

I think the client which does not manage HTML form will have to parse the needed information (a ticket value I think) in it and send a https request containing the "name" and "password" parameter. That is what we planned for our opendap to netcdf client.

The problem then is that you will only interoperate with your particular 
client, but not with other opendap clients.

I have looked at your specifications for thredds restriction. I agree with you when authentification if made at the Tomcat level.

But in our case, the authentification is made at the CAS level (because in our project it has to be centralized so that the user logs in only once and is known everywhere with that login). Then the authorization process should stay at the application level (thredds here) and there is not point to configure it in a shared file at the tomcat level.

One of the goals is to try to specify which datasets are resticted right in the catalogs. Then this can apply to not just the opendap service, but other services like wcs, etc.

Anyway the "role" concept at tomcat level or at the application level is interesting but in our case the number of users is very short that is why I didn't plan to use it.

I will try to be at the developper meeting in Boulder. I hope we will be able to discuss it further then.

That would be very nice.


John Caron a écrit :

Hi Thomas:

Thank you very much! I was able to get it working finally (I had the certificate installed in the wrong JVM!)

In looking at how CAS works with TDS, it appears that a user will get sent to the CAS login page. However, it may be that the user is not in a browser, but in another application or even a web service that does not process HTML FORMs. I am wondering if you know if its possible to configure CAS to do a HTTP 401 challenge instead of a login page? I am concerned that some OPeNDAP clients may not be able to work with a TDS server protected by CAS. I am trying to make recomendations to the OPeNDAP conference next month on how to create interoperable OPeNDAP clients and servers that implement security. Do you have plans to attend that conference? Any thoughts that you have about these issues would be helpful to me.


Thomas LOUBRIEU wrote:

Hi John,

Perhaps you can test your CAS-ification with our CAS authentification server ( To do so, you'll have to configure your TDS web.xml file as follow :

    <filter-name>CAS Filter</filter-name>


      <param-value>your application server dns:your port</param-value>

You can download the convenient cas.keystore (the public certificate for our server) at :

And then use the jvm options :

JAVA_OPTS="-Xms2048m -Xmx2048m -XX:MaxPermSize=256m"

to launch the tomcat server.

I have created a login for you, it is :
login  : jc1eed0
passwd : aze321

I hope this will help you,


John Caron a écrit :

Thomas LOUBRIEU wrote:

Hi Jon,

up to now it is what we are using "as this". Our project, in the coming weeks, is to extend the 'filter' functions (I don't know yet which they are) so that we can't check the CAS-authentification (as it now is) AND if the user login if authorized to access the current URL according to a configuration file as follow (in XML or java properties) :

URL pattern2

where URL_patternX are base URL under which the access is restricted
and loginY are the authorized CAS logins.
otherwise access is free.

It a very simple authorization configuration but we have short delays to built a demonstration system for an European operational project.

Hi Thomas, im having trouble getting CAS to work, i keep getting the following errors. I think Ive installed a certificate correctly in both tomcat keystore and in JRE cacert. So you have any advice? Unable to validate ProxyTicketValidator [[ proxyList=[null] [ casValidateUrl=[https://localhost:8443/cas/proxyValidate] ticket=[ST-2-rduetdijO1DSxhaUv6EPioZdgItQERr7ufZ-20] service=[] renew=false]]] at at at at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( at org.apache.catalina.core.ApplicationFilterChain.doFilter( at org.apache.catalina.core.StandardWrapperValve.invoke( at org.apache.catalina.core.StandardContextValve.invoke( at org.apache.catalina.authenticator.AuthenticatorBase.invoke( at org.apache.catalina.core.StandardHostValve.invoke( at org.apache.catalina.valves.ErrorReportValve.invoke( at org.apache.catalina.core.StandardEngineValve.invoke( at org.apache.catalina.connector.CoyoteAdapter.service( at org.apache.coyote.http11.Http11Processor.process( at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection( at at at org.apache.tomcat.util.threads.ThreadPool$
Caused by: PKIX path building failed: unable to find valid certification path to requested target at at at at at at at at at at at at at at at at
at at
    ... 17 more
Caused by: PKIX path building failed: unable to find valid certification path to requested target at at
at at at
    ... 31 more
Caused by: unable to find valid certification path to requested target at at at
    ... 36 more

  • 2007 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: