Add support for OIDC client assertion authentication - #1013
Open
jmapro wants to merge 1 commit into
Open
Conversation
- Introduced `client_assertion` and `client_assertion_path` config fields for OIDC federated identity - Updated authentication flow to support OIDC credentials in both GetNewSessionUpdated and GetNewSession - Added azcoreTokenAuthorizer bridge for using OIDC credentials with legacy SDK clients - Enhanced documentation and config examples for new authentication method
This file contains hidden or 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
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.
client_assertionandclient_assertion_pathconfig fields for OIDC federated identitycloses #1014
Integration test logs
Logs
N/AExample query results
Results
Test done with this obfuscated configuration