New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There may be problems with version 4.3.0. #1766
Comments
Thanks for the report, @maliming! I'm not able to reproduce this issue in any of the OpenIddict samples so I suspect it only occurs when referencing either the OIDC or JWT bearer ASP.NET Core packages: both of these packages reference So, if you reference Can you please try to explicitly add a reference to |
Thanks @kevinchalet Since it doesn't affect OpenIddict, I closed it. There will be an error if you use 👍 |
@maliming my pleasure. That would be interesting to know whether explicitly referencing |
hi We have to degrade the openiddict to 4.2, haven't tried explicitly referencing. but I guess it will work. AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2059 (comment) |
Makes sense, but the problem will reappear if people update OpenIddict in their ABP app without also using the latest |
I also was forced to downgrade to OpenIdDict to 4.2 to get it to work. |
Confirm you've already contributed to this project or that you sponsor it
Version
4.x
abpframework/abp#16479
Describe the bug
A bug was found in Identity Model version 6.30.0
AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#2059
We are using it in 4.3.
https://github.com/openiddict/openiddict-core/blob/4.3.0/Directory.Packages.props#LL41C1-L41C114
The text was updated successfully, but these errors were encountered: