feat(auth): add support for external JWT management via identity providers, fallback to self-signed JWTs #4398
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.
feat(auth): add support for external JWT management via identity providers, fallback to self-signed JWTs
Summary
This PR adds support for managing JWT tokens via external identity providers, such as Keycloak, with a fallback mechanism to use self-signed JWT tokens if no external provider is configured.
The motivation behind this change is to allow users to fully delegate JWT handling to their preferred identity provider for improved security and flexibility. In cases where no external provider is set up, the application will fall back to the existing self-signed JWT functionality to ensure backward compatibility.
Change Type
Testing
Testing was performed locally by configuring Keycloak as the identity provider to manage JWTs. Additionally, the fallback to self-signed tokens was tested by removing the external provider configuration to ensure the original behavior is preserved.
Test Configuration:
Steps to reproduce:
Checklist