Too many cookies OpenIdConnect.nonce cause error page “Bad Request - Request Too Long”

后端 未结 4 454
眼角桃花
眼角桃花 2020-12-02 19:15

I\'m using OWIN / OAuth with OpenId Connect authentication (Microsoft.Owin.Security.OpenIdConnect) in a C# ASP MVC web app. The SSO login with Microsoft account

4条回答
  •  慢半拍i
    慢半拍i (楼主)
    2020-12-02 19:46

    It turned out that the root cause was the Ajax call.

    The problematic flow was

    1) OAuth cookie got expired after some time

    2) Expiration normally causes redirection the page to login.microsoft.com to refresh the cookie. In this step OAuth framework adds new nonce cookie to the response (every time)!

    3) But Ajax doesn't handle redirections outside of the domain (cross-domain to login.microsoft.com). But the cookie was already appended to the page.

    4) Next periodical Ajax call repeated the flow causing rapid increase of 'nonce' cookies.

    Solution

    I had to extend the "OWIN OpenId" framework setup code to handle Ajax calls differently - to prevent redirection and stop sending cookies.

    public void ConfigureAuth(IAppBuilder app)
    {
        app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);
        app.UseCookieAuthentication(new CookieAuthenticationOptions());
    
        app.UseOpenIdConnectAuthentication(
            new OpenIdConnectAuthenticationOptions
            {
                ClientId = clientId,
                Authority = authority,
                Notifications = new OpenIdConnectAuthenticationNotifications
                {
                    RedirectToIdentityProvider = ctx => 
                    {
                        bool isAjaxRequest = (ctx.Request.Headers != null && ctx.Request.Headers["X-Requested-With"] == "XMLHttpRequest");
    
                        if (isAjaxRequest)
                        {
                            ctx.Response.Headers.Remove("Set-Cookie");
                            ctx.State = NotificationResultState.HandledResponse;
                        }
    
                        return Task.FromResult(0);
                    }
                }
            });
    }
    

    The Ajax caller had to be adjusted too to detect 401 code and perform full page refresh (which caused a quick redirect to Microsoft authority).

提交回复
热议问题