Add custom keystore support to JWT basic authenticator #228
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.
Purpose
This PR introduces the necessary changes to support configuring a custom keystore for the OAuth protocol. It updates all relevant areas where keystores are used. If a custom keystore is not configured, the system will fall back to the default primary or tenanted keystore.
The main changes include:
KeyStoreManager
was previously used to resolve keystore keys, it is now replaced with theIdentityKeyStoreResolver
, which dynamically selects the appropriate keystore—custom, primary, or tenanted.To configure a custom keystore for OAuth, use the following TOML configuration:
Related Issue