RE: JK + client authentication: getRemoteUser() returns null
Title: RE: JK + client authentication: getRemoteUser() returns null Finally found the problem. I started with JK, and added the /examples section from the auto-generated mod_jk.conf to my httpd.conf: Alias /examples C:/... Directory C:/... ... /Directory When I switched to JK2, I removed all the JkMounts and kept using the above. After hours of watching bytes pass by between httpd and Tomcat, hacking on the source, and general tweaking, it gradually dawned on me that I should scrap the above and use Location /examples ... /Location and getRemoteUser() started working straight away. 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]
RE: JK + client authentication: getRemoteUser() returns null
Peter, where do you search? :) better to search where the info is ... http://marc.theaimsgroup.com/?w=2r=1s=tomcatAuthenticationq=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
RE: JK + client authentication: getRemoteUser() returns null
Title: RE: JK + client authentication: getRemoteUser() returns null
I've built jk2 2.0.2 against Apache 2.0.44, run it with Tomcat 4.1.18, and still get exactly the same results: everything seems to work except for getRemoteUser() still returning null.
There is an entry [error] mod_jk child init 1 0 in the Apache log when it starts. I have no idea what this means, even after looking at the source.
workers2.properties (chmeee is the hostname):
[shm]
file=${serverRoot}/logs/shm.file
size=1048576
[channel.socket:chmeee:8009]
port=8009
host=chmeee
#info=Ajp13 forwarding over socket
tomcatId=chmeee:8009
[ajp13:chmeee:8009]
channel=channel.socket:chmeee:8009
# Map the Tomcat examples webapp to the Web server uri space
[uri:/examples/*]
worker=ajp13:chmeee:8009
#info=Map the whole webapp
# define the worker
[status:status]
# Uri mapping
[uri:/jkstatus/*]
worker=status:status
jk2.properties:
shm.file=/oss/Apache-2.0.44/logs/shm.file
request.tomcatAuthentication=false
#request.tomcatAuthentication=true
(I've tried it with both true and false. I expected the correct setting to be false, but http://marc.theaimsgroup.com/?l=tomcat-user=104322962412519=2 says true.
Tomcat connector:
Connector className=org.apache.coyote.tomcat4.CoyoteConnector tomcatAuthentication=false acceptCount=10 bufferSize=2048 connectionTimeout=0 debug=9 disableUploadTimeout=false enableLookups=true maxProcessors=75 minProcessors=5 port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false
Factory className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
What do I try next?
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]
RE: JK + client authentication: getRemoteUser() returns null
Hi, I've just installed tomcat4.1.18 with IIS and jk2 and it works fine. I was having problems with the getRemoteUser(), and it works fine when using jk2. I posted the steps to install onto my website http://www.reynir.net/tomcat/tomcat_IIS_service_jk2.html There may be some bugs in these docs, but this installation works for me so maybe it could help someone. [EMAIL PROTECTED] -Original Message- From: Robert Biernat [mailto:[EMAIL PROTECTED] Sent: 11. mars 2003 00:26 To: 'Tomcat Users List' Subject: RE: JK + client authentication: getRemoteUser() returns null 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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
RE: JK + client authentication: getRemoteUser() returns null
Title: RE: JK + client authentication: getRemoteUser() returns null
I've reverted to Tomcat 4.0.6, I'm using mod_jk that I've built myself against Apache 2.0.44, and I'm using Ajp13Connector, but getRemoteUser() still doesn't work, and I'm tearing my hair out.
Server.xml contains (in part):
Server port=8005 shutdown=SHUTDOWN debug=0
!-- jk --
Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=C:/oss/Apache-2.0.44/modules/mod_jk-2.0.44.dll
workersConfig=c:/oss/jakarta-tomcat-4.0.6/conf/jk/workers.properties
jkLog=c:/oss/jakarta-tomcat-4.0.6/logs/mod_jk.log
/
...
!-- Define the default virtual host --
Host name=localhost debug=0 appBase=webapps unpackWARs=true
!-- jk --
Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true forwardAll=true modJk=c:/oss/Apache-2.0.44/modules/mod_jk-2.0.44.dll
workersConfig=c:/oss/jakarta-tomcat-4.0.6/conf/jk/workers.properties
jkLog=c:/oss/jakarta-tomcat-4.0.6/logs/mod_jk.log
/
!-- Define an AJP 1.3 Connector on port 8009 --
Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=8009 minProcessors=5 maxProcessors=75
acceptCount=10 debug=9 tomcatAuthentication=false/
workers.properties:
worker.list=ajp13
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
httpd.conf contains (in part):
JkWorkersFile c:/oss/jakarta-tomcat-4.0.6/conf/jk/workers.properties
JkLogFile c:/oss/jakarta-tomcat-4.0.6/logs/mod_jk.log
JkLogLevel emerg
JkExtractSSL On
VirtualHost _default_:443
Alias /examples C:/oss/jakarta-tomcat-4.0.6/webapps/examples
Directory C:/oss/jakarta-tomcat-4.0.6/webapps/examples
Options Indexes FollowSymLinks
DirectoryIndex index.html index.htm index.jsp
SSLOptions +StdEnvVars +FakeBasicAuth
AuthType Basic
AuthName This realm
AuthUserFile conf/passwd
Require valid-user
/Directory
JkMount /examples ajp13
JkMount /examples/* ajp13
JkMount /examples/jsp/security/protected/j_security_check ajp13
JkMount /examples/snoop ajp13
JkMount /examples/servlet/* ajp13
JkMount /examples/CompressionTest ajp13
JkMount /examples/*.jsp ajp13
JkMount /examples/servletToJsp ajp13
JkMount /examples/SendMailServlet ajp13
/VirtualHost
and finally, the connector log:
2003-03-11 23:42:30 Ajp13Processor[8009][4] [Ajp13] receiveNextRequest()
2003-03-11 23:42:30 Ajp13Processor[8009][4] [Ajp13] receive()
2003-03-11 23:42:31 Ajp13Processor[8009][4] [Ajp13] Received 4 589 18
2003-03-11 23:42:31 Ajp13Processor[8009][4] [Ajp13] receive: total read = 589
2003-03-11 23:42:31 Ajp13Processor[8009][4] [Ajp13] Received 2 JK_AJP13_FORWARD_REQUEST
2003-03-11 23:42:31 Ajp13Processor[8009][4] [Ajp13] [RequestHandler] decodeRequest()
2003-03-11 23:42:31 Ajp13Processor[8009][4] [Ajp13] [RequestHandler] === BaseRequest ===
method = GET
protocol = HTTP/1.1
requestURI = /examples/jsp/snp/snoop.jsp
remoteAddr = 192.168.254.1
remoteHost = null
serverName = chmeee
serverPort = 443
remoteUser = null
authType = null
queryString = null
scheme = https
secure = true
contentLength = 0
contentType = null
attributes = {}
headers = === MimeHeaders ===
host = chmeee
user-agent = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
accept = application/x-shockwave-flash,text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1
accept-language = en-us, en;q=0.50
accept-encoding = gzip, deflate, compress;q=0.9
accept-charset = ISO-8859-1, utf-8;q=0.66, *;q=0.66
keep-alive = 300
connection = keep-alive
referer = https://chmeee/examples/jsp/
cookie = JSESSIONID=3832DD83EC747E4E4023C3E20054BBEA
cache-control = max-age=0
content-length = 0
cookies = === Cookies ===
Cookie JSESSIONID=3832DD83EC747E4E4023C3E20054BBEA ; 0 null null
jvmRoute = null
What am I doing wrong?
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
RE: JK + client authentication: getRemoteUser() returns null
Title: 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
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]
RE: JK + client authentication: getRemoteUser() returns null
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]
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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JK + client authentication: getRemoteUser() returns null
Title: RE: JK + client authentication: getRemoteUser() returns null Thanks to both of you. I suppose I won't be holding my breath. :-\ I'll try using the Ajp13Connector. 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: Robert Biernat [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 11 March 2003 11:26 AM To: 'Tomcat Users List' Subject: RE: JK + client authentication: getRemoteUser() returns null -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 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]
RE: JK + client authentication: getRemoteUser() returns null
Title: 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
RE: JK + client authentication: getRemoteUser() returns null
Title: RE: JK + client authentication: getRemoteUser() returns null I just looked through the 4.1.21-beta release notes: it doesn't appear to be fixed there either. Who do we have to bribe around here? :-) 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: 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 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]
