Can't login to cabi on new install

[Steve B]

Hi guys,

I've run through the UIM upgrade from 8.40 -> 8.51 -> 9.02 -> 20.3 in our lab as a proof of concept before attempting on our production system.

Cabi was never configured in our lab environment, so I followed the documentation on a fresh VM which all went exactly as expected. Now that it's complete, I can't login using the superuser credentials. It seems to accept them but throws me back to the login screen. If I enter a random username/password, I get the Invalid credentials supplied message.

The cabi log looks clean:
Oct 28 09:29:21:857 [UserSynchronizationThread, cabi] Sending nimbus user_list request to *redacted* Oct 28 09:29:21:971 [UserSynchronizationThread, cabi] Found 2 Nimbus users. Oct 28 09:29:21:971 [UserSynchronizationThread, cabi] Found Nimbus user administrator Oct 28 09:29:21:971 [UserSynchronizationThread, cabi] Found Nimbus user *redacted* Oct 28 09:29:21:973 [UserSynchronizationThread, cabi] CABI password from DB: [hidden] Oct 28 09:29:21:973 [UserSynchronizationThread, cabi] the REST user password was already set, decrypting it and using it to log into CABI Oct 28 09:29:21:973 [UserSynchronizationThread, cabi] SSO JasperUserUtility will be using jasperAdminUser: CABI_REST_USER Oct 28 09:29:22:303 [UserSynchronizationThread, cabi] JasperURLFOR_ALL_ORGANIZATIONS: http://10.116.216.177:80/cabijs/rest_v2/organizations Oct 28 09:29:22:483 [UserSynchronizationThread, cabi] JasperURLFOR_ALL_ORGANIZATIONS: http://10.116.216.177:80/cabijs/rest_v2/organizations Oct 28 09:29:22:678 [UserSynchronizationThread, cabi] roleUrl: http://10.116.216.177:80/cabijs/rest_v2/roles/ROLE_UMP_USER params: {"name":"ROLE_UMP_USER"} Oct 28 09:29:22:860 [UserSynchronizationThread, cabi] skipping creation of role ROLE_UMP_USER, it already exists on JasperServer Oct 28 09:29:22:861 [UserSynchronizationThread, cabi] roleUrl: http://10.116.216.177:80/cabijs/rest_v2/roles/ROLE_PORTAL_ADMINISTRATOR params: {"name":"ROLE_PORTAL_ADMINISTRATOR"} Oct 28 09:29:23:051 [UserSynchronizationThread, cabi] skipping creation of role ROLE_PORTAL_ADMINISTRATOR, it already exists on JasperServer Oct 28 09:29:23:051 [UserSynchronizationThread, cabi] roleUrl: http://10.116.216.177:80/cabijs/rest_v2/roles/ROLE_REPORT_DESIGNER params: {"name":"ROLE_REPORT_DESIGNER"} Oct 28 09:29:23:240 [UserSynchronizationThread, cabi] skipping creation of role ROLE_REPORT_DESIGNER, it already exists on JasperServer Oct 28 09:29:23:240 [UserSynchronizationThread, cabi] roleUrl: http://10.116.216.177:80/cabijs/rest_v2/roles/ROLE_DOMAIN_DESIGNER params: {"name":"ROLE_DOMAIN_DESIGNER"} Oct 28 09:29:23:429 [UserSynchronizationThread, cabi] skipping creation of role ROLE_DOMAIN_DESIGNER, it already exists on JasperServer Oct 28 09:29:23:429 [UserSynchronizationThread, cabi] Finished synchronizing users between UIM and CABI ​

• The probes on this host are all green in Infrastructure manager
• The JIRole / JIUser and JIUserRole tables are in the database
• It won't accept the two nimbus credentials that are being synced

Prior to installing cabi on this new VM, Operator Console was giving me this message:

After cabi installation, I get the endless spinning icon:

Not sure what else to look at - hoping someone has some advice for me.

Thanks in advance!

[David Michel]

In chrome load: chrome://flags
make these settings:

This was taken from:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/installing/ca-business-intelligence-with-ca-uim/installing-and-upgrading-ca-business-intelligence-jasperreports-server-with-ca-uim/install-or-upgrade-for-a-bundled-ca-business-intelligence-jasperreports-server.html#concept.dita_c2a97a88c62cb3b239ae19b62fa62638ef4156bf_Troubleshooting

------------------------------
Support Engineer
Broadcom
------------------------------

[Steve B]

Thanks for your reply.

While my question was stuck in approval mode, I switched the wasp probe on the cabi server over to https according to the documentation and everything seemed to gel. 

The error I was having was when i was trying to connect directly to the cabi server interface on port 80 - so OC wasn't part of it at all. The OC spinning icon was assumingly a side effect. Once I could login directly to the cabi server interface on 443, OC started working.

thanks again