安全 Web 服务 (NTLM) - Jmeter

发布于 2024-09-07 10:18:34 字数 1446 浏览 9 评论 0原文

我正在尝试使用 Jmeter 测试 Web 服务。 Web 服务受 NTLM 身份验证（Windows）保护。我可以使用 WebService(SOAP) Request 采样器加载 WSDL。目前，仅当我将代理服务器与此 SO 答案中提到的 BurpSuit 一起使用时，它才有效（我使用的是 Jmeter 和 BurpSuite，而不是 SOUP UI）。

但我不想使用代理服务器，而是想直接在 Jmeter 中使用带有 NTLM 身份验证的 Web 服务。我已经尝试过带有 ntlm 身份验证的 HTTP 身份验证管理器。但它仍然在响应中给出 401 Authorization Need

感谢您的帮助。

采样器结果。

Thread Name: WebSVC 1-1
Sample Start: 2010-06-28 13:54:08 IST
Load time: 752
Latency: 0
Size in bytes: 401
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK

Response headers:
Date=Mon, 28 Jun 2010 08:24:08 GMT
Server=Apache/2.2.9 (Unix) DAV/2 mod_jk/1.2.26
Connection=close
WWW-Authenticate=NTLM


SampleResult fields:
ContentType: text/html; charset=iso-8859-1
DataEncoding: iso-8859-1

和回应

<!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>
</body></html>

原文

I am trying to test a web service with Jmeter. The web service is protected with NTLM authentication(windows).I can able to load WSDL using WebService(SOAP) Request sampler.
Currently it works only when I use proxy server with BurpSuit mentioned in this SO answer(Instead of SOUP UI, I'm using Jmeter with BurpSuite).

But Instead of using a proxy server,I would like to use a web service directly in Jmeter with NTLM authentication.I've already tried HTTP Authentication Manager with ntlm authentication. But still it gives 401 Authorization Required in a response

Thanks for the help.

Sampler result.

Thread Name: WebSVC 1-1
Sample Start: 2010-06-28 13:54:08 IST
Load time: 752
Latency: 0
Size in bytes: 401
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK

Response headers:
Date=Mon, 28 Jun 2010 08:24:08 GMT
Server=Apache/2.2.9 (Unix) DAV/2 mod_jk/1.2.26
Connection=close
WWW-Authenticate=NTLM


SampleResult fields:
ContentType: text/html; charset=iso-8859-1
DataEncoding: iso-8859-1

and Response

<!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>
</body></html>

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

_畞蕅 2024-09-14 10:18:34

我设法使用启用了 Use keepAlive 选项的 SOAP/XML-RPC Request Sampler 使其工作（当然是在 HTTP 身份验证管理器 的帮助下。

回复收藏 0 原文

手长情犹 2024-09-14 10:18:34

您可以将安全参数添加到标头中。

 <soapenv:Header>  <wsse:Security soapenv:mustUnderstand="1" 
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> 
         <wsse:UsernameToken> 
            <wsse:Username>USERNAME_PARAM</wsse:Username> 
            <wsse:Password 
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PASSWORD_PARAM</wsse:Password> 
         </wsse:UsernameToken> 
      </wsse:Security>

You can add your security parameters to the header.

 <soapenv:Header>  <wsse:Security soapenv:mustUnderstand="1" 
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> 
         <wsse:UsernameToken> 
            <wsse:Username>USERNAME_PARAM</wsse:Username> 
            <wsse:Password 
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PASSWORD_PARAM</wsse:Password> 
         </wsse:UsernameToken> 
      </wsse:Security>

回复收藏 0 原文