search cancel

Extremely slow login/load times for fresh 20.3 OC using either local or ldap account


Article ID: 203248


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


After submitting either local or ldap credentials at the login/splash screen for a fresh installation of 20.3 Operator Console, it is taking between 2 - 6 minutes to process and proceed to drawing the OC home page. Once the home page populates, response seems reasonable, it is just the initial authentication that is taking an extremely long time. This happens across Firefox and Chrome browsers, for both LDAP and local realm users.


Release : 20.3



- need for cabi uninstall and reinstall


Verify existing instance of cabi was removed.

Please refer to:

How to Uninstall / Reinstall Bundled CABI

To uninstall cabi:

1.In the IM or Admin Console delete cabi & wasp probes (or leave wasp if it does not have \webapps\cabijs)

2.Delete these folders from disk:

   $\Nimsoft\probes\service\wasp (or leave as mentioned above)

3.Run the DROP tables
(at \Program Files (x86)\Nimsoft\probes\service\cabi\config\scripts\drop_tables\1.2\sqlserver (assuming an sql server db)

4.Deploy wasp

- open OC wasp configure 
- go to Setup tab, Probe Address, and copy the value for data_engine
- click cancel
- open cabi wasp configure 
- go to Setup tab, Probe Address, and past the value for data_engine
- click OK
- activate wasp 

5. Verify cabi robot has security certificate.pem file and robot.cfg has been updated with its location.

6. Deploy CABI 4.2 on a robot

7. Once the deployment is completed, it will show the "local" keyword reference error. Then on the CABI robot, Navigate to:

"../probes/service/wasp/webapps/cabijs/WEB-INF/applicationContext-virtualdatasource.xml" and changed the keyword from "local" to "bean"

8. Navigate to the OC robot's  "../probes/service/wasp/lib/services" folder, and copy "groovy-all-2.4.7.jar" file and place it in CABI robot's "../probes/service/wasp/webapps/cabijs/WEB-INF/lib" folder. And remove the existing "groovy-all-2.4.5.jar" file from this location and restart the CABI robot.

9. After the CABI robot restart, you should be able to access CABI through it's URL.

   http://<cabi robot>:80/cabijs 

Login Domain is left blank and superuser is both the user name and password.

10. Deploy CABI 4.3 probe on to the CABI robot which should work fine and you should be able to access the latest CABI server(4.3).

11. Redeploy these packages to the cabi robot:

    - uim_core_dashboards_pack
    - uim_unified_reporter_pack

12. Disable the below flags related to same-site cookie

enter url chrome://flags 

- SameSite by default cookies
- Enable removing SameSite=None cookies
- Cookies without SameSite must be secure
- For Microsoft Edge browser, also disable Schemeful Same-Site 

These last two steps and others are documented at:

After the above process was completed, the slowness issue no longer occurred.