Hi all,
We have a case where we sync resources via LDAP with the following root context:
OU=something,OU=String1 String2,DC=something,DC=something
Since one of the OU has a space in the name, LDAP sync jobs fail, and we can only make the sync if we workaround the space character with "%20" string:
OU=something,OU=String1%20String2,DC=something,DC=something
However, with the "%20" fix, the users can't login into the system via LDAP. They can only log when we remove the "%20" from the string.
Anyone experienced the same situation with a workaround that works both for syncing resources and allowing them to login?
PS - We can't ask them to create a branch without spaces.
Thanks,