Support legacy client secret for AzureClientSecretCredentials and OBO #23
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.
During migration of credentials to the common format, existing secrets cannot be migrated because they are not accessible from the frontend.
This change allows to use the already stored legacy client secret by datasource backend even after credential was migrated.
This should allow seamless migration of credentials for Azure Data Explorer and Azure Monitor datasources.
Related: