Description of problem:

When the LDAP catalog provider encounters an error while syncing an individual user, the entire sync process stops. This prevents other users from being ingested, even if their data is valid. Ideally, the provider should skip over the failing user, log the error with an informative message, and continue processing the remaining users.

This would require changes upstream in the LDAP plugin

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

As seen in these support tickets: RHIDP-5966, RHDHBUGS-177

Actual results:

Ingestion stops completely after receiving this error on a user:
"LdapOrgEntityProvider:default refresh failed, TypeError: Malformed entity envelope, TypeError: /metadata/name must NOT have fewer than 1 characters - limit: 1 Malformed entity envelope, TypeError: /metadata/name must NOT have fewer than 1 characters - limit: 1"

Expected results:

• Error message clearly indicates which user failed (ensure username is not leaked in the regular logs) and why the failure occurred (e.g. missing uid attribute)
• There should also be a way to allow syncing to continue on certain errors while logging and skipping the problematic users

xReproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Additional info (Such as Logs, Screenshots, etc):