ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM Operator Console (OC) - Data Access Error (and/or) CABI not auto logging from OC issue

book

Article ID: 199555

calendar_today

Updated On:

Products

CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) NIMSOFT PROBES DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

CABI has been successfully deployed following the documentation but the following issues are observed:

- For UIM releases up to 20.3.2, Data Access Error is observed in Operator Console Home Page (or) when Groups tab is selected. This happens for both admin and non admin users:

 

- For UIM releases 20.3.3 and higher, when we run report from Operator Console (path: Reports tab -> Select a report -> Run a report), the CABI page opens asking for login details (this should not happen, the CABI page should auto login). This happens for both admin and non admin users::

 

Cause

Change in the default browser behavior as to how cookies will be sent in first and third party contexts

 

Environment

Release : 9.x, 20.x and higher

Component : UIM - OPERATOR CONSOLE

 

Resolution

For browsers Microsoft Edge (and/or) Google Chrome up to release 91, use the following workaround:

 

Note:

- Officially Microsoft Edge (and/or) Google Chrome releases 91 are not compatible with UIM 20.3.x, only the following browsers are compatible with UIM 20.3.x

- The following procedure is for Windows Edge release 91, however the procedure for Chrome release 91 should also remain same

- The user would need "Administrator Privilege" permission to perform the changes

 

Procedure:

1. Right Click the Microsoft Edge browser shortcut, click on Properties:

2. In the Target window, assuming Microsoft Edge has been installed in the default folder (i.e. C:\Program Files (x86)), add the following information ahead of "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe

--disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure,schemefulsamesite  

The new line should now look like:

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure,schemefulsamesite

3. Click on Apply as shown above

4. You would now see the following dialog, click on Continue:

5. Verify the new changes have taken place, click on OK:

6. Restart the browser, relaunch the Operator Console, the above mentioned issues should now be taken care of

 

 

For browsers Microsoft Edge (and/or) Google Chrome prior to release 91, you may use the following procedure as well:

 

Procedure:

1(a). In Chrome browser type the following in the Address Bar: chrome://flags/

1(b). In Edge browser type the following in the Address Bar:  edge://flags/

2. In Flags search box type 'samesite'

3. Three settings will appear on the page

4. In their corresponding dropdown boxes select the value as Disabled:

5. Restart the browser, relaunch the Operator Console, the above mentioned issues should now be taken care of

 

Additionally, you may need to set your browser to Allow All Cookies (including third-party cookies):

 

Note:

- The following procedure is demonstrated for Google Chrome browser, however the procedure for Microsoft Edge should remain similar

 

Procedure:

1(a). In Chrome browser type the following in the Address Bar: chrome://settings/privacy

1(b). In Edge browser type the following in the Address Bar: edge://settings/content

2. Click on "Cookies and Other Site Data" as seen here:

3. On the next screen locate "Sites that can always use cookies" and click the "Add" button.

4. On the popup that appears, check the box for "including third-party cookies on this site" 

5. in the "Site" field, enter the IP address of the Operator Console robot (http://1.2.3.4/)

6. Repeat this process, adding the FQDN of the Operator Console robot. (http://name.fqdn.com)

7. Repeat this two more times, once for the IP and once for the FQDN of the CABI robot.

 

Note:

- you may have to add http:// and https:// URLs separately (again for both FQDN and IP address) if you are using HTTPS in your environment.

 

Additional Information

Related KBs:


UIM - Data access error Operator Console dashboards failed to load (broadcom.com)


UIM 20.3.x slow Operator Console, Group Trend Report redirects to CABI login, Data Access or Invalid Credentials Error (broadcom.com)


UIM - UMP/Operator Console CABI proxy configuration (broadcom.com)


UIM 20.3.2 - Operator Console Data Access Error in OC (broadcom.com)

 

 

Attachments