OC Reports - CABI is not available or accessible - Unable to communicate with any of the possible cabi probes

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

OC Reports fails with :"CABI is not available or accessible" after deploying a new CABI instance. OC Reports worked fine with the original CABI instance
UIM Dashboards load fine with a direct logon session to CABI with superuser.

The nimsoft/probes/service/wasp/webapps/cabi/META-INF/context.xml SameSiteCookies parameter is set to "Lax"  per Trouble Shooting section in Install or Upgrade for a Bundled CABI Server

Example: <CookieProcessor class="org.apache.tomcat.util.http.Rfc6265CookieProcessor" sameSiteCookies="Lax" />

**Error captured in the OC wasp probe log

Unable to contact probe 'cabi', will try other possible names
Unable to initialize cabi probe client: Unable to communicate with any of the possible cabi probes: cabi,cabi_external

**Error captured in Chrome Developer "Error 503 for /cabi/api/server_info" with "Unable to initialize cabi probe client: Unable to communicate with any of the possible cabi probes: cabi,cabi_external'

Environment

Any cabi probe version

Cause

This issue is seen when the wasp probe on the OC has a static entry for the Nimsoft cabi probe address.

Resolution

1. Open the Admin Console portlet
2. Select the Primary hub
3. Click on Robots
4. Click on the OC robot
5. Click on Probes
6. Select the wasp probe, click on the Probe Menu Option and select Raw Configure

7. Select the Setup section
8. Click on the on the Menu option for the cabi key and select Edit value; update the nimsoft cabi probe address located on the new robot or Delete the cabi key.

9. Deactivate/Activate the wasp probe

Additional Information

Accessibility Error running Cabi report or UIM Dashboard "Cabi is not available or accessible"