use a packet sniffer (wireshark) to record the http session and simply look at what the authentication scheme being used by the client and server that work. Its very easy to see in the http header what the server supports, and what the client used that worked
-Steve -----Original Message----- From: Joshua Baudhuin [mailto:[EMAIL PROTECTED] Sent: Thu 4/3/2008 1:59 PM To: JMeter Users List Cc: Subject: Re: n00b question: can't get authorization manager to work The base URL case is fine. Hmm... Does the (JMeter) authorization manager *only* support clear-text? Curiously, I cannot access the site manually using Safari-on-Windows, but can using Firefox and IE(7). The Safari indicates that the username/password will be transmitted "in the clear". I guess what I'm wondering is whether the server is actually using some non-clear-text scheme unsupported by both Safari-on-Windows and by JMeter. On Thu, Apr 3, 2008 at 10:47 AM, sebb <[EMAIL PROTECTED]> wrote: > On 03/04/2008, Joshua Baudhuin <[EMAIL PROTECTED]> wrote: > > Thanks for the speedy response. The server is Fedora, so I assume NTLM > > wouldn't be used? (The client is JMeter running on Windows.) > > > > The "Base URL" seems fine to me. I have "http://www.foo.com/bar/";. The > > page being accessed is "http://www.foo.com/bar/nun.html"; (where the > > names have been changed to protect the innocent). Does this look > > right? > > > > Yes - I think JMeter may require exact case matching, so check that. > > > > > > On Thu, Apr 3, 2008 at 10:27 AM, sebb <[EMAIL PROTECTED]> wrote: > > > > > > On 03/04/2008, Joshua Baudhuin <[EMAIL PROTECTED]> wrote: > > > > Hi, All. > > > > > > > > New to JMeter (among other things). > > > > > > > > I'm trying to test a website which has server authentication (i.e., > > > > invokes browser to pop up a messagebox requesting username/password > > > > for domain/realm. > > > > > > > > I had naively assumed that the proxy-recorder would capture this for > > > > me, but it did not. No matter: I added an HTTP Authorization Manager > > > > to the thread group for the test, and added an entry for the website. > > > > > > > > However, when I run my test, and look at the results dumped to the > > > > textfile by way of the aggregate reporter, it seems to indicate that > > > > the authorization is not occurring (or not occurring properly). > > > > > > > > E.g.: > > > > > > > > <responseData class="java.lang.String"><!DOCTYPE HTML PUBLIC > > > > "-//IETF//DTD HTML 2.0//EN"> > > > > <html><head> > > > > <title>401 Authorization Required</title> > > > > </head><body> > > > > <h1>Authorization Required</h1> > > > > <p>This server could not verify that you > > > > are authorized to access the document > > > > requested. Either you supplied the wrong > > > > credentials (e.g., bad password), or your > > > > browser doesn't understand how to supply > > > > the credentials required.</p> > > > > <hr> > > > > <address>Apache/2.0.54 (Fedora) Server at www.xxx.com Port > > > > 80</address> > > > > </body></html> > > > > </responseData> > > > > > > > > Any hints? > > > > > > > > I should mention that the "domain" and "realm" fields of the > > > > authorization manager entry are blank. I have tried filling them in, > > > > but that didn't seem to help either. > > > > > > > > > > It can be difficult getting the entries correct. > > > Domain and realm are not needed except for NTLM, which the Fedora > > > server is unlikely to use. If it does use NTLM, and it uses NTLMv2, > > > then I'm afraid it will never work. > > > > > > The Base URL needs to match the target otherwise the credentials won't > > > be sent to the server - are you sure that is correct? > > > > > > Try enabling debug for the Auth Manager - select the element and use > > > the Help Menu. > > > Run a short test and check the log - this may give a clue. > > > > > > > Thanks in advance. > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
