fix: Resolve transient dependency conflict with Microsoft.IdentityModel.Protocols in JwtBearer authentication #785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #745
Problem
Applications using
Microsoft.AspNetCore.Authentication.JwtBearer
alongside Okta [SDK.NET](http://sdk.net/) 8.2.0 encounter a runtime error (IDX10500: Signature validation failed
) due to transient dependency mismatches. This occurs because the SDK indirectly references outdated versions ofMicrosoft.IdentityModel.Protocols
andMicrosoft.IdentityModel.Protocols.OpenIdConnect
, breaking OpenID Connect metadata retrieval.Solution
Microsoft.IdentityModel.Protocols
(v8.2.0) andMicrosoft.IdentityModel.Protocols.OpenIdConnect
(v8.2.0) in the project file to enforce compatibility withJwtBearer
8.x.Impact
JwtBearer
authentication with Okta.Verification Steps
Validate that
IDX10500
errors no longer occur during authentication.Why This Works
Protocols
andOpenIdConnect
are used.IDX10500
error.