I'm trying to use Nifi to connect to a secure WebSocket (wss:// .... ). I'm having trouble connecting to the stream because of a very basic authentication issue.
I've used wscat (npm) and a Java client to successfully connect in the past. All that was needed is an Http Header.
The wscat implementation would only require the following option:
.option('-H, --header <header:value>', 'Set an HTTP header. Repeat to set multiple. (--connect only)', appender(), )
But, when I add the header as a property to the ConnectWebSocket processor and/or the JettyWebSocketClient, Nifi complains that it is not a supported property.
Since SSL context services are not required to connect to this particular stream, is there a way that I can still connect just using a custom header?
@dvmishra, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post.
Have you tried passing header details under property "Authentication Header Charset" under JettyWebSocketClient ?