[ 
https://issues.apache.org/jira/browse/NIFI-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann resolved NIFI-4114.
------------------------------------
    Resolution: Won't Fix

Although NiFi generates self-signed certificates with application access, 
providing demo configurations is outside of the scope of standard capabilities.

> Keystore Management Service with already configured demo keystore.
> ------------------------------------------------------------------
>
>                 Key: NIFI-4114
>                 URL: https://issues.apache.org/jira/browse/NIFI-4114
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: milind pandit
>            Priority: Minor
>              Labels: security
>
> Within NiFi flow, its required to import additional third party trusted 
> certificates into the trust store in order to make the REST/SOAP service call 
> over SSL.
> To simplify the overall operational overhead, provide UI with keystore 
> management service to administer keys and certificates from one location.
> Either this can be part of Ranger functionality or model within HDF to manage 
> third party security certificates.
> The certificate manage page can display the existing certificates in the 
> keystore and from where you can perform many operations like
> Generate key pair, import and export trusted certificates, delete 
> certificates etc.
> In addition to this feature within NiFi provide out of box already configured 
> SSLContextService controller service with demo keystore.
> This will help in accelerating the development for business use case. When 
> there is need to invoke SSL based service, user
> can use the UI to import the Trusted cert into the demo keystore and use the 
> already configured SSLContextService controller service
> within to NiFi processor. 
> This significantly reduces the complexity and time to build the use case 
> which requires SSL communication.



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

Reply via email to