[ 
https://issues.apache.org/jira/browse/NIFI-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754618#comment-17754618
 ] 

ASF subversion and git services commented on NIFI-11926:
--------------------------------------------------------

Commit 4d233b0202a794b84ab45f8bfdfe11f406d3f879 in nifi's branch 
refs/heads/support/nifi-1.23 from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4d233b0202 ]

NIFI-11926: Added proxy handling in Azure Storage Credentials Services

Added Proxy Configuration Service property in 
AzureStorageCredentialsControllerService_v12 and 
ADLSCredentialsControllerService used by Service Principal and Managed Identity 
authentication modes.

This closes #7590

Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit 2e6eaaeb38c2166a06f7876740968230af81f7f5)


> Add proxy handling in Azure Storage Credentials Services
> --------------------------------------------------------
>
>                 Key: NIFI-11926
>                 URL: https://issues.apache.org/jira/browse/NIFI-11926
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>             Fix For: 2.0.0, 1.24.0, 1.23.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When NiFi is behind a proxy and has no direct access to Azure services via 
> the internet, the Azure Storage processors fail if Service Principal or 
> Managed Identity authentication is used.
> These authentication methods need access to {{login.microsoftonline.com}} but 
> no proxy can be configured for this at the moment.
> Similar to the AWS and GCP credential services, add "Proxy Configuration 
> Service" property in the controller service where the authentication 
> parameters are configured.
> Controller services: AzureStorageCredentialsControllerService_v12, 
> ADLSCredentialsControllerService



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to