Fix: Resolve Token Validation Failure by Upgrading IdentityModel Dependencies #284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ntitymodel packages
prachi-okta
approved these changes
Jun 16, 2025
|
@aniket-okta Is there any reason why release 4.6.4 hasn't been pushed to NuGet yet? |
|
Hi @jforage-sw, We’re currently facing an Artifactory authentication issue on our end, which is preventing us from completing the release process. Thanks for your patience! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This pull request resolves a critical
SecurityTokenSignatureKeyNotFoundExceptionthat occurs during JWT validation whenOkta.AspNetCoreandOkta.Sdkare used together.The fix involves upgrading core Microsoft identity packages and refactoring the authentication logic to be compatible with the modern libraries.
What's Changed?
System.IdentityModel.Tokens.JwtandMicrosoft.IdentityModel.JsonWebTokensto their latest versions to resolve dependency conflicts.IdentityModel.Clientpackage.UserInformationProviderclass has been updated to use the standardSystem.Net.Http.HttpClientinstead of the legacy client.AuthenticationBuilderextension to correctly handle token validation with the newJsonWebTokentype, ensuring that signing keys are properly retrieved from the OIDC discovery document.Why This Change Was Needed
A dependency conflict between
Okta.AspNetCore(which relied on IdentityModel v6) andOkta.Sdk(which uses v7+) caused the token validation process to fail with the errorIDX10500: Signature validation failed. The newer libraries return aJsonWebTokeninstead of aJwtSecurityToken, which the existingAddOktaWebApimethod could not handle. This change modernizes our authentication pipeline and makes it robust.Related Issues