Azure AD Workload Identity authentication support #38
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.
This PR adds support for Azure AD Workload Identity which is used for access to AAD service identities in Kubernetes.
This allows users who host Grafana in Kubernetes be able to use Workload Identities as alternative to Managed Identities which are not directly accessible by pods in Kubernetes.
Details on Azure AD Workload Identity:
The newly introduced credentials type is
AzureWorkloadIdentityCredentials
.Intended to be serialized in datasource JSON as:
The credentials object doesn't provide any configuration options on the datasource side, but on the level it will be possible to override Tenant ID, Client ID, and Token File path.
Proposed configuration settings in Grafana config (not part of this PR):