On 08/02/2012 19:52, Jonathan Rosenberg wrote:
> Mark,
>
> Thanks for the reply.
>
>>> I don't understand why Tomcat is involved in the authentication (the
>>> exception happens in org.apache.catalina.realm.JDBCRealm getPassword)
>>> at this point. As far as I know, the only authentication going on
>>> should be the CAS authentication used by my app.
>
>> This means you are using Tomcat's BASIC authentication.
>> It appears you do not have CAS configured correctly. Check your web.xml.
>
> I'm (obviously) a novice here. Which web.xml should I be checking?
>
> - The app's web.xml? (There is mention of anything security-related there).
>
> - The 'root' web.xml?
Ah. The joy's of debugging Servlet 3.0 applications. Web fragments were
such a good idea. Not.
In CATALINA_BASE/conf/context.xml, add the following to the <Context
.../> element:
logEffectiveWebXml="true"
That will cause Tomcat to log the result of merging the default web.xml,
host level web.xml, app level web.xml, web fragments and annotations as
an 'effective' web.xml file. Then look at your app for the CAS config
and and <login-config .../> sections.
> Is there any easy way to tturn on logging for Tomcat's authentication?
I don't think that is going to help much right now.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org