@TN08
The InvokeHTTP processor supports HTTP methods for connecting to a target server. The InvokeHTTP processor does not establish a listener for inbound http connections.
The properties for Basic Authentication Username and Password on this processor are used when the target endpoint supports basic auth and the username and password would need to provided by that target endpoint. If basic auth is not supported by target endpoint, TLS is also supported.
If you want to setup a listener in NiFi for inbound HTTP you would use either ListenHTTP processor or the newer HandleHttpRequest/HandleHttpResponse processors. NiFi processors do not support basic auth for inbound connections. So to connect with these processors the source systems would need to pass a client/user certificate in a mutual TLS handshake as a way to identify the client. This means the processor would need to have a StandardRestrictedSSLContextService controller service that is configured with a keystore (containing a serverAuth certificate the client system can trust) and truststore (containing the complete trust chain for the clientAuth certificate presented by your client).
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
