LDAP port 389 is going into infinite loop while searching for usersin GRC ARQ from full AD. It works when you limit the base string to some specific OU. Is there any resolution to it?
We need to update AD groups from GRC for which we need 389 port as 3268,3269 are for read only. It's required for 389 to function in whole wide area to provision all users. Right now when we are limiting it to some specific area, then only it works.
For others facing this issue, our issue got resolved by selecting chase in referral chasing and error as ignore and increasing page size in LDAP server and connectors.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.