Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.8.0, 1.9.0
-
None
Description
Currently all event hub processors seem to use Shared Access Signature (SAS)tokens. A emerging pattern (might be the dominate pattern) is to integrate with Managed identities for Azure resources. Instead of NiFi using the Shared Access Token (SAS) token provider, NiFi should create a token provider for the managed identity with the following call:
{{TokenProvider.CreateManagedServiceIdentityTokenProvider(ServiceAudience.EventHubAudience)}}call.
As such, there are no secrets to save and use.
Some of the above text copied from azure, giving azure docs proper credit.
Code examples and full details on how applications (like NiFi) would integrate with Azure Managed Identities (Azure Active Directory).
https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-managed-service-identity
Attachments
Issue Links
- is duplicated by
-
NIFI-8989 Azure Managed Identities for EventHub - ConsumeAzureEventHub and GetAzureEventHub
-
- Resolved
-