Using HTTP/HTTPS with basic authentication or SSL protection

You can use basic authentication or SSL-protected communication.

Using HTTP/HTTPS with basic authentication

You can use basic authentication with HTTP and HTTPS. This is enabled by setting a username:password credential in the probe's Nhttpd.BasicAuth property and using this in the EventFactory node by checking the Use basic authentication checkbox, and inserting the credentials. For details about enabling HTTP/S basic authentication on the probe, see the following topic in the IBM Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/probegtwy/task/omn_prb_enableremoteauthentication.html:

Using SSL protection

To use SSL communication between the probe and the remote host on which Node-RED is running, the probe must be configured with SSL enabled. For details, see IBM Documentation:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/probegtwy/task/omn_prb_enableremotessl.html.

To configure ObjectServer SSL-protected network, see the following topic in IBM Documentation:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/concept/omn_con_ssl_usingssl.html.

When the SSL certificate is installed, update the URL field In the EventFactory node. Configure the URL to use HTTPS and the port that is configured in NHttpd.SSLListeningPort property; for example: https://localhost:443/probe/common

Note: If you are using a self-signed certificate, Node-RED may reject the connection because it is considered unauthorized and Node-RED will show a SELF_SIGNED_CERT_IN_CHAIN error on the console. To work around this, set the NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0, and restart Node-RED.

Example for Unix:

$ export NODE_TLS_REJECT_UNAUTHORIZED=0
$ node red.js -v push2omnibus.json

For Windows, edit this environment variable in System Properties.