Arran Cudbard-Bell wrote:
On Jun 29, 2015, at 11:22 AM, Michael Ströder <michael@stroeder.com> wrote:
Arran Cudbard-Bell wrote:
On 29 Jun 2015, at 09:48, Michael Ströder <michael@stroeder.com> wrote: Hmm, I'd prefer you to simply pass the configured original string to libldap and use result code of ldap_url_parse() just as proof that it's a valid LDAP URI.
base_dn, filter, scope and attributes need stripping. We don't support specifying them via the URL.
I guess we could error out if any of those components were found
To me this seems to be the best solution for now.
OK, done.
Sorry, this needs some more work. Checked 0b81520cb825473a91d1ae21cc874e6220fec461: server = 'ldap://localhost:1390' now results in log message: rlm_ldap (ldap): Connecting to ldap://ldap://localhost:1390 ^^^^^^^^^^^ rlm_ldap (ldap): ldap_initialize failed: Bad parameter to an ldap routine server = 'ldapi://%2Ftmp%2Fopenldap-socket' now results in log message: Invalid server, must be in <server>[:<port>] format server = 'localhost:1390' works ok. Ciao, Michael.