You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Raimee Stevens <ra...@yahoo.com> on 2001/08/30 16:41:57 UTC

Problem with Authentication and Warp Connector

config: Apache 1.3.20 (Win32), Tomcat 4.0b7 (Catalina)

Problem: Unable to authenticate user against protected
URL when invoked using warp connector.

Reason: Warp Connector not passing user credentials.

For instance, a request for a resource under a 
protected context is accessed via the Apache
Warp Connector like this:
     
     http://localhost/protectedContext/

Result is that user is *never* authenticated.

A request for the same resource accessed via the
Tomcat 
Stand-Alone connector honors the user credentials
     http://localhost:8080/protectedContext/

Result is that a user *is* authenticated.

I have installed a RequestDumperValve under both 
Connectors in order to see what headers Catalina
receives. Under the standalone connector, the 
remoteUser header is initialized after the first
WWW-Authenticatd header is sent. Under the Warp
Connector, it is not (ie. remoteUser=null). 

Regards,
Raimee

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com