Since yesterday users are facing below error while accessing (login) TSCO GUI Console.

BCO_WEB_WARN301 - Inexistent user or wrong password.

All LDAP / AD users are failing to access the console.

As a try, admin created the local test1 user on RSSO and added it with Capacity_Administration group, but still getting same error while accessing the TSCO GUI console

Once the user credentials are entered, apparently the console login loads for 2-3 minutes, and after that generates and error.

Same LDAP/ AD and test1 user is able to access the TSPS GUI console.

Even with locally created test1 user we can access the TSPS GUI console.

Admin restarted the RSSO, TSPS and TSCO, including DB server, but still having same issue.

TSPS Added CO Component is also in a Error status, Registration error.

All TSCO Services are up and running fine, and we did not see any error messages from TSPS and TSCO log files.

1) From log files check if you can find any error or warning messages, that may point to reported issue.

2) Via command line you can execute the below API calls to check the TSPS connectivity with LDAP user...
curl -k -i -H 'Content-Type:application/json' -X POST --data '{"username":"admin","password":"admin12345","tenantName":"*"}' https://TSPS_FQDN/tsws/api/v10.1/token

If this query works successfully, you will get the authToken

3) Use below API call to check the Groups access, by using above API call generated authToken and verify if that also works fine.
curl -k -i -H "authToken: _bbb50e12-eeb2-489d-ba8b-f82d6ed5dc8f" https://TSPS_FQDN/tsws/api/v10.1/token/groups

4) Connect to TSCO DB and check the CONF_PROPS tables entries for RSSO and TSPS:

select * from CONF_PROPS where name like '%tsps%'
OUTPUT:
------------
environment.tsps.host          TSPS.bmc.com
environment.tsps.port                    8043
environment.tsps.protocol              https 

select * from CONF_PROPS where name like '%sso%'
OUTPUT:
------------
environment.remedy.sso.host                 RSSO.bmc.com
environment.remedy.sso.port                      8048
environment.remedy.sso.protocol                https
environment.remedy.sso.defaultRealm          *


5) Check the entries found as output of the above queries:
- Verify the TSPS host, port, and protocol match the ones used in your browser to access TSPS
- Verify the RSSO host, port, and protocol matche the oned on TSPS Administration -> Remedy SSO configuration page

6) If they don't match, update the TSPS and RSSO configuration entries on TSCO DB, with the correct FQDN/port/protocol.

For example:
update conf_props set value ='<TSPS Server>' where name='environment.tsps.host';
update conf_props set value='<RSSO Host>' where name='environment.remedy.sso.host';

commit;

7) Restart the TSCO components to apply changes:
./cpit restart