[Backport] Add ability to do "client credentials" OAuth2 flow to Spark Connector #1070
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.
PR Checklist
docsis updatedDescription of changes
This change adds the ability to configure the UC Spark Connector to do an OAuth2 "client credentials" exchange to authenticate.
Since access tokens minted through a client credentials exchange generally have a limited lifetime, there is functionality here to refresh the token before the current access token expires.
This enhancment introduces two new Spark properties
oauth2-server-uri- this is the URI to the token exchange endpointcredential- the principal's credential to use to exchange for an access token (in the form of client_id:client_secret)This PR covers Issue #1071