asp.net-mvc – DotNetOpenAuth：消息签名不正确

发布时间：2020-12-15 18:56:58 所属栏目：asp.Net 来源：网络整理

导读：尝试使用MyOpenID和Yahoo进行身份验证时,我会收到一条“消息签名不正确”异常. 我几乎使用了DotNetOpenAuth 3.4.2附带的ASP.NET MVC示例代码 public ActionResult Authenticate(string openid){ var openIdRelyingParty = new OpenIdRelyingParty(); var aut

尝试使用MyOpenID和Yahoo进行身份验证时,我会收到一条“消息签名不正确”异常.

我几乎使用了DotNetOpenAuth 3.4.2附带的ASP.NET MVC示例代码

public ActionResult Authenticate(string openid)
{
    var openIdRelyingParty = new OpenIdRelyingParty();
    var authenticationResponse = openIdRelyingParty.GetResponse();

    if (authenticationResponse == null)
    {
        // Stage 2: User submitting identifier
        Identifier identifier;

        if (Identifier.TryParse(openid,out identifier))
        {
            var realm = new Realm(Request.Url.Root() + "openid");
            var authenticationRequest = openIdRelyingParty.CreateRequest(openid,realm);
            authenticationRequest.RedirectToProvider();
        }
        else
        {
            return RedirectToAction("login","home");
        }
    }
    else
    {
        // Stage 3: OpenID provider sending assertion response
        switch (authenticationResponse.Status)
        {
            case AuthenticationStatus.Authenticated:
            {
                // TODO
            }
            case AuthenticationStatus.Failed:
            {
                throw authenticationResponse.Exception;
            }
        }
    }

    return new EmptyResult();
}

与Google,AOL等人合作.但是,雅虎和MyOpenID属于AuthenticationStatus.Failed案例,但出现以下异常：

DotNetOpenAuth.Messaging.Bindings.InvalidSignatureException: Message signature was incorrect.
   at DotNetOpenAuth.OpenId.ChannelElements.SigningBindingElement.ProcessIncomingMessage(IProtocolMessage message) in c:UsersandarnogitdotnetopenidsrcDotNetOpenAuthOpenIdChannelElementsSigningBindingElement.cs:line 139
   at DotNetOpenAuth.Messaging.Channel.ProcessIncomingMessage(IProtocolMessage message) in c:UsersandarnogitdotnetopenidsrcDotNetOpenAuthMessagingChannel.cs:line 992
   at DotNetOpenAuth.OpenId.ChannelElements.OpenIdChannel.ProcessIncomingMessage(IProtocolMessage message) in c:UsersandarnogitdotnetopenidsrcDotNetOpenAuthOpenIdChannelElementsOpenIdChannel.cs:line 172
   at DotNetOpenAuth.Messaging.Channel.ReadFromRequest(HttpRequestInfo httpRequest) in c:UsersandarnogitdotnetopenidsrcDotNetOpenAuthMessagingChannel.cs:line 386
   at DotNetOpenAuth.OpenId.RelyingParty.OpenIdRelyingParty.GetResponse(HttpRequestInfo httpRequestInfo) in c:UsersandarnogitdotnetopenidsrcDotNetOpenAuthOpenIdRelyingPartyOpenIdRelyingParty.cs:line 540

显示其他人有同样的问题：http://trac.dotnetopenauth.net:8000/ticket/172

有没有人有解决方法？

解决方法

事实证明,这是在Web场环境中使用DotNetOpenAuth的问题.

当您创建OpenIdRelyingParty时,请确保在构造函数中传递null.

这将使您的网站进入OpenID无状态或“哑”模式.用户登录稍慢一些(如果您注意到),但您避免不必编写一个IRelyingPartyApplicationStore来允许DotNetOpenAuth在您的农场中工作;

var openIdRelyingParty = new OpenIdRelyingParty(null);

（编辑：李大同）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!