Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Seems like I have to use '%20's instead of spaces in the BaseDN string. I'm guessing someone forgot to encode the string before constructing the URL.
Should I continue to use %20's or will this be fixed in the future?
jji
Hello,
Could you please have a look at this jira issue to see if it is what you are looking for?
https://jira.talendforge.org/browse/TDI-27138
Best regards
Sabrina
Yes, that's it sorry I didn't see that in my searches.
But that was back in 2013, which means we'll continue to go forward with non-standard BaseDN values?
Other Java (ldapsearch) clients work just fine.
@imholzj imholzj , TDI-27138 did not make any changes, it suggests a workaround that use '+' replace space, you can continue to use this workaround.
Shouldn't there be a component that works with spaces?
Hi imbolzj, our developer commented 'the problem seems to be from the LDAP API.', that's why we have nothing to change on this component.
