[SDK-3862] Add support for JWT client authentication #1029
Merged
Conversation
This file contains 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
This fixes an issue when running tests that will provide jwks to openid-client as it does a comparison on the constructor of the object provided which does not match as the globals are different. For tests like the stateless session tests that need to use a jest mock like timers we can use the node environment to ensure timers work as expected
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Merged
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.
📋 Changes
Adds support for authenticating using JWT Client Authentication.
This is supported by the
clientAssertionSigningKeyandclientAssertionSigningAlgconfig settings, which map to theAUTH0_CLIENT_ASSERTION_SIGNING_KEYandAUTH0_CLIENT_ASSERTION_SIGNING_ALGenvironment variables.ef83deb also moved the jest testing setup to use
jest-environment-node-single-contextto fix an issue where the test for this feature would fail due to the object comparison used by openid-client due to a known issue with jest. The stateless session tests that use jest timers had a docblock added that set the environment to the builtin node environment to ensure the timers work📎 References
SDK-3862
🎯 Testing