Hey all,
I'm currently running IIS as the front-end to Tomcat 4.1.12 using the
JK2 2.0.1 release of isapi_redirector2.dll. When I use the
CoyoteConnector, it authenticates for me (creates a Principal for me)
and does not pass information to my Realm implementation. When I use
the Ajp13Connector with tomcatAuthentication=true, it forces the user to
authenticate with the configured Realm. I've tried adding
tomcatAuthentication=true to the CoyoteConnector, but it still
authenticates for me. Is there a way that the CoyoteConnector can
accomplish the same thing as setting tomcatAuthentication=true in the
Ajp13Connector?
Here's the CoyoteConnector configuration that I am using that creates
the Principal for me.
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="false" redirectPort="443"
acceptCount="10" debug="10" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"
scheme="https" secure="true"
tomcatAuthentication="true"
/>
Here's the Connector configuration that forces the user to authenticate
in Tomcat:
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="false" redirectPort="8443"
acceptCount="10" debug="1" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"
tomcatAuthentication="true"/>
Thanks,
Mike Becker
--
To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
