Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of melindasavoy@texashealth.org
 designates 208.189.200.2 as permitted sender)
From: "Savoy, Melinda" <MelindaSavoy@texashealth.org>
To: 'Tomcat Users List' <users@tomcat.apache.org>, "'pid@pidster.com'"
	<pid@pidster.com>
Date: Wed, 23 Jun 2010 09:58:51 -0500
Subject: RE: Still having problem retrieving user value from ISAPI Filter
 for authentication
Thread-Topic: Still having problem retrieving user value from ISAPI Filter
 for authentication
Thread-Index: AcsSyo9lIADIAS2PSu6k8qJguLkffQAB49EwAAR7BOA=
Message-ID: 
 <45572F79660DDC429F6B44582360A9AB010B0715B0@PHDEXMB01.txhealth.org>
References: 
 <45572F79660DDC429F6B44582360A9AB010B0710A1@PHDEXMB01.txhealth.org>
 <45572F79660DDC429F6B44582360A9AB010B0711FD@PHDEXMB01.txhealth.org>
 <AANLkTimhIJ2LvaMFJYrpThX6hfoAbFSu7uOLL_tlK-nB@mail.gmail.com>
	 <4C20A853.6040901@pidster.com>
 <45572F79660DDC429F6B44582360A9AB010B071209@PHDEXMB01.txhealth.org>
 <4C20B213.3080107@pidster.com>
	 <45572F79660DDC429F6B44582360A9AB010B071217@PHDEXMB01.txhealth.org>
 <4C20B6E0.2070702@pidster.com>
 <45572F79660DDC429F6B44582360A9AB010B07122D@PHDEXMB01.txhealth.org>
	 <4C20C32D.8050109@pidster.com>
 <45572F79660DDC429F6B44582360A9AB010B071258@PHDEXMB01.txhealth.org>
 <4C20F091.6000400@kippdata.de>
	 <45572F79660DDC429F6B44582360A9AB010B071396@PHDEXMB01.txhealth.org>
 <D72C174D3CAC0A4E812FAD012D646E9F1562B87FE2@CMS1.enterprise.maricopa.gov>
	 <AANLkTilaVoee8bhQxDbAF8dC3bJvkgQSIQlz1Z2O7kHy@mail.gmail.com>
 <4C21660D.60807@kippdata.de> <A4B17C5B-5BB7-4246-BAA5-8C84746E6D32@pidst!
 er.com> <4C21D7C9.5060909@kippdata.de> <4C21F561.3000501@pidster.com>
 <45572F79660DDC429F6B44582360A9AB01084BF081@PHDEXMB01.txhealth.org>
In-Reply-To: 
 <45572F79660DDC429F6B44582360A9AB01084BF081@PHDEXMB01.txhealth.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Let me ask another question if I might in addition to the one below:

In my ISAPI log it shows:

[Wed Jun 23 09:50:59.568 2010] [5024:6028] [debug] jk_isapi_plugin.c (310=
8): Service protocol=3DHTTP/1.1 method=3DGET host=3D127.0.0.1 addr=3D127.=
0.0.1 name=3Dlocalhost port=3D80 auth=3DNTLM user=3DTEXAS\SavoyM uri=3D/i=
ndex.jsp

The value of "80" is shown, my question is does this line in my ISAPI log=
 show the request as to where it is coming from, meaning IIS since IIS is=
 on port 80?

My tomcat app is running on port 9080.

Just curious.

I think, I am going on to try Waffle, instead of trying to pursue this an=
y further.  dB has been kind enough to offer his help in getting me setup=
=2E

I just thought I'd ask this one last question. Thanks for all the time an=
d help.

Regards.

-----Original Message-----
From: Savoy, Melinda=20
Sent: Wednesday, June 23, 2010 7:50 AM
To: 'Tomcat Users List'; 'pid@pidster.com'
Subject: RE: Still having problem retrieving user value from ISAPI Filter=
 for authentication

Let me ask, what maybe a stupid question now, but when I print out the en=
umeration value of the request header names, see below, using request.get=
HeaderNames() should the user be listed as one of the headers which is pa=
ssed on from the ISAPI filter:

=3D=3D=3D MimeHeaders =3D=3D=3D
accept =3D */*
accept-language =3D en-us
connection =3D Keep-Alive
host =3D localhost
user-agent =3D Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident=
/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; Info=
Path.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8; MS-RTC E=
A 2)
authorization =3D NTLM TlRMTVNTUAADAAAAAAAAAEgAAAAAAAAASAAAAAAAAABIAAAAAA=
AAAEgAAAAAAAAASAAAAAAAAABIAAAABcKIogUBKAoAAAAP
accept-encoding =3D gzip, deflate
content-length =3D 0

Thank you.


-----Original Message-----
From: Pid [mailto:pid@pidster.com]=20
Sent: Wednesday, June 23, 2010 6:52 AM
To: Tomcat Users List
Subject: Re: Still having problem retrieving user value from ISAPI Filter=
 for authentication

On 23/06/2010 10:45, Rainer Jung wrote:
> On 23.06.2010 09:51, Pid wrote:
>> On 23 Jun 2010, at 02:40, Rainer Jung<rainer.jung@kippdata.de>  wrote:
>>
>>> On 22.06.2010 21:59, Marc Boorshtein wrote:
>>>>>
>>>>> Unless you are going to authenticate via one of Tomcat's=20
>>>>> authentication methods; BASIC, FORM, etc, then getRemoteUser() is=20
>>>>> going to return null.
>>>>>
>>>>> You'll need to add a security constraint, login-config and=20
>>>>> security-role to your web.xml to test getRemoteUser(); in just Tomc=
at.
>>>>>
>>>>
>>>> This shouldn't be the case since she put tomcatAuthentication=3D"fal=
se"
>>>> tomcat should be taking the username from the JK_REMOTE_USER=20
>>>> attribute.
>>>>
>>>> Have you tried a wireshark packet capture?
>>>
>>> The log file of the ISAPI redirector she presented already contains=20
>>> a dump of the AJP packet the redirector is going to send out. The=20
>>> dump shows the correct user string contained in the packet.
>>>
>>> I've got no idea what's wrong here.
>>
>> Would you expect the user value normally to be set as another=20
>> (REMOTE_USER type) header by ISAPI?
>=20
> No, it gets send as an AJP specific request attribute that the AJP=20
> connectors know about. It's not an HTTP header.

OK, and I'm guessing that if there was a way to get the AJP connector to =
dump those attributes you'd have said so by now.


p

> Regards,
>=20
> Rainer
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>=20


The information contained in this message and any attachments is intended=
 only for the use of the individual or entity to which it is addressed, a=
nd may contain information that is PRIVILEGED, CONFIDENTIAL, and exempt f=
rom disclosure under applicable law.  If you are not the intended recipie=
nt, you are prohibited from copying, distributing, or using the informati=
on.  Please contact the sender immediately by return e-mail and delete th=
e original message from your system.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org