You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "W. Wood Harter" <wo...@side8.com> on 2002/01/11 23:43:21 UTC

apache mod_auth and tomcat

I've searched the archives and didn't find how to use apache mod_auth 
for basic authorization to protect tomcat pages. My problem is that 
apache is on port 80 and tomcat is on 8080. If I protect a link at 
http://myhost:80/myapp/ with Apache's mod_auth, a smart user could just 
use http://myhost:8080/myapp.

Anyone know how to configure Tomcat to only speak with my Apache server?

If this is impossible, I guess I could use Tomcat, but I have a database 
already populated with unix crypt passwords which work fine with 
mod_auth_mysql. I don't want to have to change my password storage system.

Thanks,
Wood



--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>


Re: apache mod_auth and tomcat

Posted by David Smith <dn...@cornell.edu>.
That depends on whether you are using mod_webapp or not.  IMHO it would be 
better to simply comment out the connector that services port 8080 from 
server.xml.  That way, AJP13 protocol for mod_jk is still available (if 
that's what you use).

--David

On Friday 11 January 2002 05:45 pm, you wrote:
> You could completely disable the "Standalone" container in the server.xml.
> Leave the warp-connected apache container and remove everything in the
> standalone one.  Then there will be no port :8080.
>
> That's just one idea though.
>
> Charlie
>
> -----Original Message-----
> From: W. Wood Harter [mailto:wood@side8.com]
> Sent: Friday, January 11, 2002 5:43 PM
> To: tomcat-user@jakarta.apache.org
> Subject: apache mod_auth and tomcat
>
>
> I've searched the archives and didn't find how to use apache mod_auth
> for basic authorization to protect tomcat pages. My problem is that
> apache is on port 80 and tomcat is on 8080. If I protect a link at
> http://myhost:80/myapp/ with Apache's mod_auth, a smart user could just
> use http://myhost:8080/myapp.
>
> Anyone know how to configure Tomcat to only speak with my Apache server?
>
> If this is impossible, I guess I could use Tomcat, but I have a database
> already populated with unix crypt passwords which work fine with
> mod_auth_mysql. I don't want to have to change my password storage system.
>
> Thanks,
> Wood
>
>
>
> --
> To unsubscribe:   <ma...@jakarta.apache.org>
> For additional commands: <ma...@jakarta.apache.org>
> Troubles with the list: <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe:   <ma...@jakarta.apache.org>
> For additional commands: <ma...@jakarta.apache.org>
> Troubles with the list: <ma...@jakarta.apache.org>

--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>


RE: apache mod_auth and tomcat

Posted by "Charles N. Harvey III" <ch...@alloy.com>.
You could completely disable the "Standalone" container in the server.xml.
Leave the warp-connected apache container and remove everything in the
standalone one.  Then there will be no port :8080.

That's just one idea though.

Charlie

-----Original Message-----
From: W. Wood Harter [mailto:wood@side8.com]
Sent: Friday, January 11, 2002 5:43 PM
To: tomcat-user@jakarta.apache.org
Subject: apache mod_auth and tomcat


I've searched the archives and didn't find how to use apache mod_auth 
for basic authorization to protect tomcat pages. My problem is that 
apache is on port 80 and tomcat is on 8080. If I protect a link at 
http://myhost:80/myapp/ with Apache's mod_auth, a smart user could just 
use http://myhost:8080/myapp.

Anyone know how to configure Tomcat to only speak with my Apache server?

If this is impossible, I guess I could use Tomcat, but I have a database 
already populated with unix crypt passwords which work fine with 
mod_auth_mysql. I don't want to have to change my password storage system.

Thanks,
Wood



--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>