Add support for IdP broker endpoint based IdC auth #149
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.
Description
This pull request adds support for a new authentication plugin, IdpTokenUrlAuthPlugin, which enables Redshift clients to dynamically fetch access tokens from an external IDP broker endpoint (such as Keycloak) over HTTPs. This plugin removes the need for embedding static tokens in JDBC URLs—solving token-replay issues when using DB connection pools—and integrates seamlessly with the existing Redshift authentication framework.
Motivation and Context
New Authentication Plugin Support
Introduced IdpTokenUrlAuthPlugin in
src/main/java/com/amazon/redshift/plugin/IdpTokenUrlAuthPlugin.java.
#146
Diagram
Supports:
Types of changes
Checklist
License
- By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.