AddMicrosoftAccount callback to /signin-microsoft request query too large #496
Unanswered
norr-carr
asked this question in
IdentityServer
Replies: 1 comment 2 replies
-
|
This looks like an issue with how the integration with Microsoft account is done in ASP.NET Core. We do have some documentation on how to configure your web server to allow for larger URIs, but unfortunately, the query string is being created by Microsoft when authenticating using a Microsoft account, so this is beyond the control of Duende IdentityServer. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are using Duende Identity Server (7.4.4) with both local and external providers. We have enabled Microsoft Single Sign On using
This has worked in production in the past.
Recently we began getting the 404 status code on the request back to Identity Server at /signin-microsoft. We determined this was due to the large request size and increased the request limits, which temporarily solved the problem. I'm not aware of any changes made to the EntraID settings that would have caused the change, but we did recently update Identity Server. I'm now searching for any way to determine how we can minimize the size of the request and return our request limits back to their defaults.
I tried the recommended approach in https://docs.duendesoftware.com/identityserver/ui/login/external/#state-url-length-and-isecuredataformat of adding
services.AddOidcStateDataFormatterCache();which did reduce the request size in other callbacks, but did not appear to change this request size.I read https://github.com/orgs/DuendeSoftware/discussions/219 which appears to suggest the same fixes that I've already tried and https://github.com/orgs/DuendeSoftware/discussions/23 which talks about the size of Cookies returned when authenticating to Microsoft using OpenIdConnect set up manually.
Is there any way to reduce the request size from Microsoft? Is there any way to see what information is included in the code and session state query parameters that are so large?
Example request:
Beta Was this translation helpful? Give feedback.
All reactions