Sunile Manjee created NIFI-6149:
-----------------------------------
Summary: Azure EventHub Managed identities integration
Key: NIFI-6149
URL: https://issues.apache.org/jira/browse/NIFI-6149
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework, Extensions
Affects Versions: 1.9.0, 1.8.0
Reporter: Sunile Manjee
Currently all event hub processors seem to use [Shared Access Signature
(SAS)|https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas]tokens.
A emerging pattern (might be the dominate pattern) is to integrate with
[Managed identities for Azure
resources|https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview].
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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
