Supid errors gone but another internal error with JDBC Realm

[tw...@t-online.de]

Hello,

the error I posted in "JDBCRealm/Tomcat do not not protect Web Pages!?..."
is solved. Stupid I was I forgot to rename the *.html files to *.jsp.
Tomcat obviously totally ignores the html-File and doesn't protect it. Ok
seems to work. But now when accessing the protected source I get an error
like this one:

Error: 500
Location: /texdb/txdb/menues/smgen.jsp
Internal Servlet Error:

java.lang.NullPointerException
     at interbase.interclient.PreparedStatement.setString(Unknown Source)
     at
org.apache.tomcat.request.JDBCRealm.authenticate(JDBCRealm.java:306)
     at
org.apache.tomcat.request.JDBCRealm.authenticate(JDBCRealm.java:482)
     at
org.apache.tomcat.core.ContextManager.doAuthenticate(ContextManager.java:837)
     at
org.apache.tomcat.core.RequestImpl.getRemoteUser(RequestImpl.java:341)
     at org.apache.tomcat.request.JDBCRealm.authorize(JDBCRealm.java:503)
     at
org.apache.tomcat.core.ContextManager.doAuthorize(ContextManager.java:855)
     at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:789)
     at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
     at
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java:160)
     at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
     at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
     at java.lang.Thread.run(Thread.java:484)

I m using Interbase/Interclient 6.01, Linux and made server.xml and web.xml
the usually way (see above JDBCRelam 15/05). When doing a manually selcect
... where -- from like written in JDBCRealm.java via JDBC Explorer it
works. What could be wrong? Jasper.log, servlet.log and tomcat.log don't
give me a hint.

Grreting and many thanks in advance

   Thomas

Re: Supid errors gone but another internal error with JDBC Realm

[Antony Bowesman <ad...@teamware.com>]

tw.richter@t-online.de wrote:
> 
> Hello,
> 
> the error I posted in "JDBCRealm/Tomcat do not not protect Web 
> Pages!?..." is solved. Stupid I was I forgot to rename the *.html
> files to *.jsp. Tomcat obviously totally ignores the html-File and 
> doesn't protect it. Ok seems to work. But now when accessing the 
> protected source I get an error like this one:

Tomcat's behavious is strange re html files.  If one is protected via
url-pattern it redirects to the configured login form.  So, you type in
the user name/password but tomcat never calls the realm/authenticate()
method, it just then shows the html page regardless of what you type in
on the login form...