Login to cabi server displays blinking or flashing page and constantly reloads

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Login to cabi bundled flashing screen. Constant reloading. Selecting dashboards or reports shows Data Access Error. This is running cabi and OC http.

Environment

• Release: 20.3 or higher
• Component: UIM - CABI
• cabi_bundled

Cause

• This is due to browser security changes that no longer allows you to disable the cross-site domain connection between systems any longer.
• This is necessary primarily for CABI when it is configured for and accessed via HTTP

Resolution

On the CABI robot (note that this is not performed nor valid on cabi v8.0+):

Deactivate the cabi probe.

1. Raw Configure the CABI probe and set the CABI configuration parameter cabi_url to:
   
   http://<URLwithMatchingSubdomainAndDomain>:<port>/cabijs
   
   
2. Deactivate the wasp probe
   
   
3. Modify nimsoft/probes/service/wasp/webapps/cabijs/META-INF/context.xml with

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

     4. Activate the cabi probe.

     5. Activate the wasp probe

On the Operator Console robot:

1. Deactivate the wasp probe

Modify nimsoft/probes/service/wasp/webapps/cabi/META-INF/context.xml with

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

     2. Activate the wasp probe


When connecting to the OC interface make sure to connect using the following url syntax/format:

http://<URLwithMatchingSubdomainAndDomain>:<port>/operatorconsole_portlet

Note: When using HTTP it is required to use the full domain name (not IP address) when logging into OC, and for the connection to the cabi server. Same site functionality in browsers has been slowly removed, to where it would allow to ignore the errors related to a same site connection issue, to now where they no longer allow the ability to get around it.

Additional Information

https://developer.chrome.com/blog/referrer-policy-new-chrome-default/