I sent a message earlier with a similiar problem however I'm using IIS 5.0
and the ISAPI redirector, and not using Apache with SSL certificates.

It appears the combination of the CoyoteConnector and the JkCoyoteHandler is
where the bugs lies. I switched off the CoyoteConnector, and reverted back
to the old Ajp13Connector, added the attribute tomcatAuthentication="false"
and it worked fine. However I've been having stability problems with the
Ajp13Connector (Tomcat runs out of threads) and want to upgrade to the new
CoyoteConnector as soon as possible. At this stage this bug is all that is
holding me back from deployment of 4.1.18 to production.

Rob 

-----Original Message-----
From: Filip Hanik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 11 March 2003 11:12 AM
To: Tomcat Users List
Subject: RE: JK + client authentication: getRemoteUser() returns null


you are correct, there is a bug filed for this,
Bugzilla Bug 11563 
 

not sure anyone is dealing with it though,
Filip
-----Original Message-----
From: Mayne, Peter [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2003 4:01 PM
To: Tomcat Users List
Subject: JK + client authentication: getRemoteUser() returns null


I'm using 
Windows XP 
Apache 2.0.44 
OpenSSL 0.9.7a 
mod_jk-2.0.43.dll 
Tomcat 4.1.18 
I've followed the instructions at
http://www.johnturner.com/howto/winxp-howto.html to set up Apache and Tomcat
using JK, with authentication using client certificates.
Everything seems to be working fine, except request.getRemoteUser() is
returning null. (The REMOTE_USER is shown from a CGI script, so
authentication is working.)
The only reference I can find to this problem is in
/tomcat-docs/config/jk.html: setting the tomcatAuthentication attribute when
using org.apache.ajp.tomcat4.Ajp13Connector, but since this connector
doesn't appear in my server.xml, it doesn't seem to be relevant. (It does
seem to be relevant for Tomcat 4.0.6, but I'd rather not have to try
dropping back to there.)
Before I post voluminous config files, am I missing something obvious? 
Thanks. 
PJDM 
-- 
Peter Mayne 
Technology Consultant 
Spherion Technology Solutions 
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 
T: 61 2 62689727  F: 61 2 62689777 
The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any
interference with, 
use, disclosure or copying of this material is unauthorised and prohibited;
and

(b) may contain personal information of the recipient and/or the sender as
defined 
under the Privacy Act 1988 (Cth). Consent is hereby given by the
recipient(s) to 
collect, hold and use such information and any personal information
contained in a 
response to this email, for any reasonable purpose in the ordinary course of

Spherion's 
business, including forwarding this email internally or disclosing it to a
third party. All 
personal information collected by Spherion will be handled in accordance
with 
Spherion's Privacy Policy. If you have received this email in error, please
notify the 
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s)
supplied in 
this email and any attachments without first entering into a contractual
agreement with 
Spherion. You further agree not to divulge any information contained in this
document 
to any person(s) or entities without the express permission of Spherion.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to