IBM Guardium

Hi Asa Ullah,

1. What version of Guardium are you running?
2. What error do you get when you try to use a LDAP account to login to the Collector?
3. Do multiple attempts to login to the Collector with a LDAP account disable that user account on the CM and other MU's?

Assuming you have other managed units that are working, here are some steps I would take to troubleshoot. (Retry authentication to the Collector after each step to try to narrow down root cause.)

1. Ensure the Collector is communicating healthily with the CM and force the config to the Collector. From the CM, Central Management Console:
   1. Collector status is green and last ping is within the last 5 minutes.
   2. Select the Collector and run "Refresh".
   3. Prior to v12.2 option only: select the Collector and run "Distribute Authentication Config".
2. From the CM, run 'Run Once Now' on the "Portal User Synch" then re-run "Refresh" on the unit (step 1.2 above).
3. Restart the Collector (restart system)
4. A more drastic option would be to consider un-register/re-register the Collector.
5. Run auth_issues must-gather on the CM and Collector, reproduce this issue. Review for errors and/or open a support case.

11.5 Guardium version.

Error shows, Invalid User Name and/or password.

Using same credentials other collectors are working.

Tried User Portal Synch, Distribute Authentication Config and restart system.

Nothing worked.

I would pursue a connectivity issue between the collector and the LDAP server.