Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (nike.apache.org: domain of shettyd@gmail.com designates
 209.85.160.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=HWS2G+3llxac+ySoUePeG42c6TCxZZDj30YHDnPF6NnV7tRBuI6eV5949LC5f7sawl
         hdeVy2z/Ds9OjLfmT1Be4pBsCeqTZ7RkWwusKsjUCKYi3GDNaoHiyPTfbxEe3tvx4v01
         bTKJEJ7E1tKJkFueGhQP1wf0qIj2jpa31qgwQ=
MIME-Version: 1.0
In-Reply-To: <25aac9fc1003192000i3b02bc70sd6fecdab6b910c1d@mail.gmail.com>
References: <9362e74e1003181117g3f20871dr525d12412d12fa60@mail.gmail.com>
	 <25aac9fc1003192000i3b02bc70sd6fecdab6b910c1d@mail.gmail.com>
Date: Fri, 19 Mar 2010 20:15:59 -0700
Message-ID: <4483c26c1003192015n6007e1e5x4d0859eacb36fd0f@mail.gmail.com>
Subject: Re: Reg NTLM Authorization Manager
From: Deepak Shetty <shettyd@gmail.com>
To: JMeter Users List <jmeter-user@jakarta.apache.org>
Content-Type: multipart/alternative; boundary=000e0cd1120c150b78048232e2df

--000e0cd1120c150b78048232e2df
Content-Type: text/plain; charset=ISO-8859-1

Hi
>From a brief reading of http://davenport.sourceforge.net/ntlm.html
<http://davenport.sourceforge.net/ntlm.html>The NTLMv2 Response
Step 2
*The Unicode uppercase username is concatenated *with the Unicode
authentication target (the domain or server name specified in the Target
Name field of the Type 3 message). Note that this calculation always uses
the Unicode representation, even if OEM encoding has been negotiated; *also
note that the username is converted to uppercase*, while the authentication
target is case-sensitive and must match the case presented in the Target
Name field.

It might be that the implementation is correct as per the specification (and
since windows usernames are case insensitive your application really should
be the one that changes)

what happens when you use Internet explorer as the client instead of Jmeter
, do you not see a similar problem?

regards
deepak


On Fri, Mar 19, 2010 at 8:00 PM, sebb <sebbaz@gmail.com> wrote:

> On 18/03/2010, Gokulakannan Somasundaram <gokul007@gmail.com> wrote:
> > Hi,
> >    We have found an issue, wherein JMeter is sending the NTLM user name
> in
> >  capital case. NTLM authentication is not affected because of this, but
> our
> >  application specific authorization does a case sensitive comparison for
> >  application specific authorization and it fails over there. We were able
> to
> >  reproduce the scenario by typing user name in capital case manually.
> Also we
> >  verified that the application log file is printing the username in CAPS,
> >  when we do the testing through JMeter. Can someone help me how to
> resolve
> >  this? A pointer to the source code where i should change will be very
> >  helpful.
> >     I tried my best to find the code, but it seems like JMeter is sending
> >  the credentials right and i suspect the problem is with the httpclient
> >  commons api. But i am not sure of that. Someone please help me here.
>
> Does JMeter behave the same with both HTTP samplers?
>
> >  Thanks in advance,
> >  Gokul.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

--000e0cd1120c150b78048232e2df--