Hi there,
I have recently configured LDAP in a customers environment, which works absolutely fine. However when migrating the service to HTTPS, I’m getting an error 33. Looking in the LDAP Error log files, 33 relates to Alias problem.
As stated, this has worked absolutely fine before for LDAP, specifically for LDAPS.
Just wondering if anybody else has seen this?
Thanks,
Did you change your LDAP configuration to the LDAPS one (including server certificate(s)?
Yes I’ve got the CACert Path - *.cer, cert-path - *.cer & key path - *.key all set.
Thanks
Try to post your LDAP configuration
app-user: account name of AD
cacert-path: C:\Certificates\Issuingcert.cer
cert-path: C:\Certificates\hostnameofmachinetoLDAPserver.cer
key-path: C:\Certificates\hostnameofmachinetoLDAPserver.key
ldap-url: ldaps://Domain:636/dc=XXXX,dc=X??one?(&(objectClass=user)(objectCategory=user)(samaccountname=X))
password: XXXX
verbose: 2
Similar to the above 
Do you use client certification validation? If no, then remove the cert-path and key-path options
Following the Genesys docs as per their deployment guide…
https://docs.genesys.com/Documentation/FR/Current/ExtAuth/LDAPOpts
Do any have any suggestions on implementation of LDAPS where it’s successfully worked?
Thanks,
I have deployed LDAPS many times and never encounter similiar issue and also, as was mentioned, never use the client certificate authorization (and I still think you do not need it as well).
Just tried it without the cert-path and key-path, sadly no luck. I’ll continue having a play around.
I would recommend to use any LDAP browser software to be ensure the connection over secure protocol is working apart Genesys env.
So interestingly using an LDAP browser and i’m able to connect to the LDAP server using LDAPS and External Authentication (SSL Certificate) and it works!
Which kind of certificate are you using? PEM?
I’ve used cer and PEM (both Base 64)