Peter, where do you search? :) better to search where the info is ... http://marc.theaimsgroup.com/?w=2&r=1&s=tomcatAuthentication&q=t elaborating on b): jk2 is the internal name for 2 things: 1) a new native connector arch based on jk but enterely new.. 2) the new Coyote based ajp13 connector, that is the java code that manages ajp13 connections.. and it's compatible with native jk and jk2.. that is this new connector replace the ajp13connector you found in 4.0.6 server.xml jk2.properties it's a cfg file for Coyote/jk2.. here it's a explanation of the subtles for this 3 different things, jk native, jk2 native, and Coyote/jk2 connector for tomcat.., http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/doc/ Saludos, Ignacio J. Ortega
-----Original Message----- From: Mayne, Peter [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 1:22 AM To: 'Tomcat Users List' Subject: RE: JK + client authentication: getRemoteUser() returns null a) My apologies. I certainly try to send plain text, but Outlook has a mind of its own, however tiny it may be. I think I've now beaten it into submission. b) I'll give it a try. From what I've seen mentioned of jk2, "it's not ready for production use, not as tested and reliable as jk, etc", so I've haven't tried it. I also presumed that jk and jk2 being different things, that a jk2.properties file wouldn't modify a jk configuration. c) I've searched for tomcatAuthentication, but I didn't realise that putting it in the properties file (as opposed to specifying it in server.xml) would make a difference.(Not to mention that searching the archive is currently returning 0 results.) 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 > -----Original Message----- > From: Ignacio J. Ortega [ mailto:[EMAIL PROTECTED] > Sent: Wednesday, 12 March 2003 1:56 AM > To: 'Tomcat Users List' > Subject: RE: JK + client authentication: getRemoteUser() returns null > > > Peter, > > a) Dont send HTML messages to this list, Read > http://jakarta.apache.org/site/mail.html. > b) jk2.properties it's used for the coyote connector jk > configuration ( > aka jk2 java part), not matter which native connector > (jk,jk2) you use.. > > c) The recipe of i gave to you has been proved to death, by > many people, > search archives for tomcatAuthentication.. > > Saludos, > Ignacio J. Ortega > > > > -----Original Message----- > From: Mayne, Peter [ mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 2:27 AM > To: 'Tomcat Users List' > Subject: RE: JK + client authentication: getRemoteUser() returns null > > > > add ... to jk2.properties > "jk2", even though I'm using jk? > Anyway, I tried it and it still didn't work. > Thanks anyway. > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > > -----Original Message----- > > From: Ignacio J. Ortega [ mailto:[EMAIL PROTECTED] > > Sent: Tuesday, 11 March 2003 12:21 PM > > To: 'Tomcat Users List' > > Subject: RE: JK + client authentication: getRemoteUser() > returns null > > > > > > add > > > > request.tomcatAuthentication=false > > > > to jk2.properties > > > > Saludos, > > Ignacio J. Ortega > > > > > -----Original Message----- > > > From: Filip Hanik [ mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, March 11, 2003 1: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] > > > > > 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] > 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]
