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

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

Commit d5028315592028b91f793ab5d1d48fee2754075b in nifi's branch 
refs/heads/support/nifi-1.19 from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d502831559 ]

NIFI-10882 Set credentials for ElasticSearchClientService based on 
AuthorizationScheme

This closes #6722

Signed-off-by: David Handermann <[email protected]>


> ElasticSearchClientService should not allow both BASIC and API_KEY properties 
> to be set simultaneously
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-10882
>                 URL: https://issues.apache.org/jira/browse/NIFI-10882
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.19.0
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Major
>             Fix For: 1.20.0, 1.19.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> While the {{ElasticSearchClientService}} will show/hide Controller Service 
> properties based on the currently selected {{AuthorizationScheme}}, it is 
> possible for a user to set {{BASIC}} credentials (e.g. 
> {{Username}}/{{Password}}) then later switch to {{API_KEY}} auth without 
> removing the {{BASIC}} properties - this leads to multiple {{Authorization}} 
> headers being configured in requests to Elasticsearch, which is unexpected.



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

Reply via email to