Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Raw data will be transferred from the source through an HandleHttpRequest. How can I encrypt in motion this traffic?
Created 12-23-2019 09:45 AM
You will need to send the raw data to NiFi HandleHTTPRequest using https protocol. This will require that NIFI be secured (per required documentation). If your source is secure also, the HandleHTTPRequest should be configured using an SSLContextService with a keystore and truststore containing the certs for the source.
Created on 12-23-2019 09:48 AM - edited 12-23-2019 09:51 AM
You will need to configure your HandleHttpRequest processor with a SSL Context Service in order to encrypt data in transit being sent to this processor from a client. This of course then means you client needs to be able to at a minimum to trust the server certificate presented by this SSL context service in the TLS handshake. The truststore you use in the NiFi SSL Context Service will only need to contain the public cert for your client or complete certificate trust chain for your client if you have configured your HandleHttpRequest processor to "Need authentication" in the Client Authentication property. Mutual Authentication is not needed to ensure encryption of data in transit.
Hope this helps,
Matt
Created 12-23-2019 09:45 AM
You will need to send the raw data to NiFi HandleHTTPRequest using https protocol. This will require that NIFI be secured (per required documentation). If your source is secure also, the HandleHTTPRequest should be configured using an SSLContextService with a keystore and truststore containing the certs for the source.
Created on 12-23-2019 09:48 AM - edited 12-23-2019 09:51 AM
You will need to configure your HandleHttpRequest processor with a SSL Context Service in order to encrypt data in transit being sent to this processor from a client. This of course then means you client needs to be able to at a minimum to trust the server certificate presented by this SSL context service in the TLS handshake. The truststore you use in the NiFi SSL Context Service will only need to contain the public cert for your client or complete certificate trust chain for your client if you have configured your HandleHttpRequest processor to "Need authentication" in the Client Authentication property. Mutual Authentication is not needed to ensure encryption of data in transit.
Hope this helps,
Matt