December 2016

OMG, guys we have left few days only for 2016 

IBM IIB

I just give you brief description on how we can enable basic authentications to secure access to HTTP and SOAP public endpoints that are running in our IIB on Cloud integrations.

These endpoints are HTTPInput and SOAPInput message flow nodes. If basic authentication is enabled for an integration, HTTP requests to any HTTP or SOAP nodes in that integration require the correct URL, a user name, and a password.

So, if basic authentication is disabled for an integration, HTTP requests can access any of your HTTP or SOAP nodes in that integration by using only the correct URL, and do not require a user name or password. Basic authentication settings are associated with an integration and apply to all HTTP and SOAP nodes in that integration. For integrations for which we have enabled basic authentication, the user name that is required to access HTTP and SOAP nodes is fixed to IIB and a corresponding password is generated automatically. In the Integration Details view, you can view the password; to change it, you generate a new password. To access HTTP or SOAP nodes in an integration that has basic authentication turned on, in HTTP requests to those nodes you must include an HTTP BasicAuth header that uses the corresponding user name and password.

Finally, we can view the correct HTTP BasicAuth header. If we regenerate the password, the HTTP BasicAuth header is updated to use the new password.