开发者

IE8 gets stuck while sending openid authentication request with activated attribute exchange

开发者 https://www.devze.com 2023-01-06 07:36 出处:网络
I´m getting a problem sending the authentication request with activated attribute exchange. It works with FF and Opera but IE seems to have a problem with it.

I´m getting a problem sending the authentication request with activated attribute exchange. It works with FF and Opera but IE seems to have a problem with it.

The error occurs within the request.RedirectToProvider(). The Url within the address bar shows the endpoints url.

Here is a code snippet where the authentication request is created and sent

using (OpenIdRelyingParty openid = this.createRelyingParty())
            {
          开发者_如何学编程      IAuthenticationRequest request = openid.CreateRequest(openid_identifier, realm);
                ;

                var fetch = new FetchRequest();
                fetch.Attributes.AddRequired(WellKnownAttributes.Contact.Email);
                request.AddExtension(fetch);

                // Send your visitor to their Provider for authentication.
                request.RedirectToProvider();

}

I guess that inside RedirectToProvider() a POST is sent and short after a GET. By RFC a POST followed by a GET is not allowed. Unfortunately I don`t know how to validate it.

Does someone got the same problem?


On further investigation this seems to happen (based upon the providers logs): The authentication request is sent via POST. The Provider answers with a redirect. This is how it happens that there is at first a POST and then a GET.

I dont think this is how the openId specification say to do it. Shouldnt there be a POST response if i request with a POST and a GET if I request with a GET?

Anyhow.. Is there a way to make the RedirectToProvider()-method sending the request via GET instead of POST?

0

精彩评论

暂无评论...
验证码 换一张
取 消