无法使用 NTLM 身份验证针对 DotNetNuke 运行 WCAT

发布于 2024-08-24 01:56:12 字数 2307 浏览 10 评论 0原文

我有一个 ubr 文件设置,可以使用 WCAT 对内部 DotNetNuke 站点进行压力测试:

transaction
{
    id = "Intranet Home Page";
    weight = 1000;

    cookies{clear = true;}
    sleep{delay = rand("1","500");}

    request
    {
        url         = "/";
        statuscode = 401;
    }

    request
    {
        url         = "/";
        authentication = ntlm;
        username = "mydomain\\accountname";
        password = "password";
        statuscode = 200;
    }

    close{ method = reset;}
}

运行此命令时 (wcat.wsf -run -clients localhost -s myserver -t test.ubr -f settings.ubr -x) 我只是收到很多错误500秒:

2010-03-08 10:29:31 192.168.11.239 GET / - 80 - 192.168.52.139 - 401 2 2148074254 2010-03-08 10:29:31 192.168.11.239 GET / - 80 - 192.168.52.139 - 401 1 0 2010-03-08 10:29:31 192.168.11.239 GET /Default.aspx - 80 mydomain\myaccount 192.168.52.139 - 500 0 0

DNN 将这些错误报告为:

AssemblyVersion:< /strong> 5.2.3
门户ID: 0
门户名称: 我的公司
用户 ID: -1
用户名:
ActiveTabID: 39
ActiveTabName:主页
原始URL: /Default.aspx
绝对URL: /Default.aspx
绝对URLReferrer:
用户代理:
默认DataProvider: DotNetNuke.Data.SqlDataProvider、DotNetNuke.SqlDataProvider 异常GUID: 28d8821f-1ef2-41db-8a65-d33e97a69130
内部异常: 未处理的错误:
文件名:
文件行编号: 0
文件列编号: 0
方法: DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest 堆栈跟踪:
消息:System.Exception:未处理的错误:
---> System.NullReferenceException:未将对象引用设置为对象的实例。在 DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) 在 System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&completedSynchronously) --- 内部异常堆栈跟踪结束 ---
来源:
服务器名称: MYSERVER

它似乎以某种方式丢失了用户名。

I have a ubr file setup to stress test an internal DotNetNuke site with WCAT:

transaction
{
    id = "Intranet Home Page";
    weight = 1000;

    cookies{clear = true;}
    sleep{delay = rand("1","500");}

    request
    {
        url         = "/";
        statuscode = 401;
    }

    request
    {
        url         = "/";
        authentication = ntlm;
        username = "mydomain\\accountname";
        password = "password";
        statuscode = 200;
    }

    close{ method = reset;}
}

When running this (wcat.wsf -run -clients localhost -s myserver -t test.ubr -f settings.ubr -x) I simply get lots of error 500s:

2010-03-08 10:29:31 192.168.11.239 GET / - 80 - 192.168.52.139 - 401 2 2148074254
2010-03-08 10:29:31 192.168.11.239 GET / - 80 - 192.168.52.139 - 401 1 0
2010-03-08 10:29:31 192.168.11.239 GET /Default.aspx - 80 mydomain\myaccount 192.168.52.139 - 500 0 0

DNN is reporting these errors as:

AssemblyVersion: 5.2.3
PortalID: 0
PortalName: My Company
UserID: -1
UserName:
ActiveTabID: 39
ActiveTabName: Home
RawURL: /Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 28d8821f-1ef2-41db-8a65-d33e97a69130
InnerException:
Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest
StackTrace:
Message: System.Exception: Unhandled Error:
---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: MYSERVER

It seems to be losing the username somehow.

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

扫码二维码加入Web技术交流群

发布评论

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

评论(1

诠释孤独 2024-08-31 01:56:12

这是由于我使用的 DNN Windows 身份验证模块造成的。看起来它会重定向到身份验证页面,设置 cookie,然后重定向回来。由于某种原因,WCAT 无法处理这个问题。我最终使用了WAST。

This was due to the DNN Windows Authentication module I was using. It looks like it redirects to an authentication page, sets a cookie, and then redirects back. WCAT couldn't cope with this for some reason. I ended up using WAST.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文