Hi.
You need to add to the web.xml file the following lines:
login-config
auth-methodCLIENT-CERT/auth-method
/login-config
When you try to connect to the protected resource, the navigator will
request a client certificate.
Regards.
--
Hi,
i tried the following:
+
Hi,
i use already the client-cert method and a suitable security-role.
May i made a mistake during build?
How can be ensured that tomcat make use of the new authenticate method?
thanks
Patrick
jazorin wrote:
Hi.
You need to add to the web.xml file the following lines:
login-config
Hi,
i tried the following:
+ Add the mehtod authenticate(...) to the File JDBCRealm.java
+ build a Tomcat distribution
+ replace the catalina.jar with the new version (on an other machine)
+ add role-namefull DN/role-name to the web.xml
+ insert into table users ('DN','DN')
+ insert into table
Hi.
You can to implement a JDBCRealm with client certificates modifying the
org.apache.catalina.realm.JDBCRealm class. You need add the public
Principal authenticate(X509Certificate[] cert) method. Inside, you have
to include the following lines:
import
Hi,
I have implemeted the methods getPassword() and getPrincipal() in
JDBCRealm. Digest authentication works for me with these changes. One thing
that still doest work is if I have stored the password in encrypted form in
the database. I have doubts if this will always work in the scenario
it possible.
Thanks,
Uddhav
- Original Message -
From: Uddhav Shirname [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 7:53 PM
Subject: Re: JDBCRealm getPassword() unimplemented in Tomcat 4.1.18 (returns
null)
Hi,
I have implemeted the methods
Hi.
Maybe your problem is that you are using a recent MySQL with an old JDBC
driver. Get the latest MM driver (2.0.4 at the moment) from
http://mmmysql.sourceforge.net/
I use Mysql for my applications and just drop the MM binary in the
corresponding /WEB-INF/lib directory, and that's all.
Hola David:
Sorry for the delay, just catched your message in the archive.
* Would it be acceptable for me to submit a patch for this code that
currently gets repeated in 2-3 different places ( in a few
different ways
for Tomcat 3.2 ), moving the act of reconnecting to the
database to
Hola Paul:
I'm the responsible of the presence of JDBCRealm in tomcat 3.x and 4.x
from a code contributed by Carson Mc. Donald, FYI. I'm responsible too
of any bugs in JDBCRealm, by auto asignation :-), and only maintainer.
The initial error is here, and I can't figure out where it
comes
