Closed lvandyk closed 2 years ago
This organization is not maintained anymore besides critical security bugfixes (if feasible). This organization will be archived when .NET Core 3.1 end of support is reached (3rd Dec 2022). All new development is happening in the new Duende Software organization.
The new Duende IdentityServer comes with a commercial license but is free for dev/testing/personal projects and companies or individuals making less than 1M USD gross annnual revenue. Please get in touch with us if you have any question.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Questions are community supported only and the authors/maintainers may or may not have time to reply. If you or your company would like commercial support, please see here for more information.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
We updating to the latest version of IdentityServer4 but we have one breaking change that removes the ability to use multipart-form-data on the token endpoint: https://github.com/IdentityServer/IdentityServer4/issues/4340
We currently have clients and apps configured to use multipart-form-data. We are making the fix to use form-url-encoded but what about the existing installations?
Is there a way to disable this check or to somehow create a middleware that will convert the request to form-url-encoded just before hitting the token endpoint logic?
Thanks!