AD bindDN with spaces is being escaped

[O'Dowd, Josh]

Greetings,

I know this is likely an ldaptive api issue but I wasn't sure where to post something for them, and I am trying to configure a secondary attribute-resolver data connector, LDAP flavor to connect to our AD.  The primary connector is to OpenLDAP so I don't have a previous bind to reference here.

The issue is that the bindDN I need to use contains spaces in the OU, which is allowed in AD.  When I pass along the entire bindDN to the connector config and run, it is failing validation due to Invalid Credentials.  The root cause, looking at the log output is that the ldaptive bind request is using a bindDN where the spaces in the OU have been escaped (\), which of course makes it invalid.

I have tried putting the entire bindDN in double and single quotes which removes the escapes, but then includes the quotes.  I have also tried adding the escapes to the config value manually, which ldaptive simply leaves in place.

Any thoughts?

Thanks for the time.

Josh O'Dowd
Software Systems Engineer / Identity Access Management
Central IT, University of Montana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170328/06cc4fb0/attachment.html>