[NIFI-10776] Add support for PKI Authentication in ElasticSearchClientServiceImpl

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.19.0
• Component/s: Extensions
• Labels: elasticsearch
• Assignee: Chris Sampson
• Reporter: Nandor Soma Abonyi
• Created: 08/Nov/22 11:27
• Updated: 21/Nov/22 19:53
• Resolved: 21/Nov/22 19:53

Description

Also add NONE as an AuthenticationScheme option.

By Chris S:

I'd probably stick with BASIC being the default as that would mean Username/Password remain available by default when adding the Processor to the canvas, which matches the current behaviour and therefore is backwards compatible.

If the user selects NONE then I guess we'd be hiding the existing Username/Password and new API Keyproperty inputs (via dependsOn).

If the user selected PKI then it would be great if the SSLContext Controller become mandatory, but I don't think that's currently possible, so in effect this would have the same effect as NONE on the available processor properties (we don't want to hide SSL Context if something other than PKI is selected here, as https/TLSmight very well still be needed even if it's not used for Auth in Elasticsearch).

One option might be to use some customerValidation for this though - if the user has selected PKI, they mustalso specify an SSL Context in their processor configuration. Similarly, if NONE is selected, then we could validate that none of the Username/Password/API Key fields are provided?

Issue Links

• links to: GitHub Pull Request #6662