LDAP connection error in some OneX communicator versions

[salav]

Hi guys:

LDAP connection problems
No problems in One-X Comm 6.1.1.
But I cant connect in 6.2.5 and 6.2.6.
This is a little extract from the log. Has anybody any idea about this?

06/16/2015 09:21:47:587] DBH: CONFIG: [0b80] GetParameter(EnableOneXPortal=True).
[06/16/2015 09:21:47:587] DBH: CONFIG: [0b80] GetParameter(UserEnableOneXPortal=False).
[06/16/2015 09:21:47:587] DBH: CONTACT: [0b80] SearchDirectories: Search directory type 'LDAP'.
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] SearchDirectory: Query "" (Count: 50)
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Name : "CODI"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Type : "0"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Address : "ldap-cs.XXXXXXXXXX.com"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Port : "XXXX"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP User name : ""
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Time-out : "100"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Result Limit : "50"
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] LDAP Bind Option : "1")
[06/16/2015 09:21:47:587] DBH: DIRDATA: [0b80] Connect : Connecting to LDAP ldap-cs.XXXXXXXXXX.com:XXXX
[06/16/2015 09:21:47:587] DBH: HISTORY: [1444] CHistoryManager: OnMessageReceived
[06/16/2015 09:21:47:665] DBG: DIRDATA: [0b80] DIRDATA::CWinLDAPAdaptor::Connect: Checking if SSL is enabled
[06/16/2015 09:21:47:665] DBG: DIRDATA: [0b80] DIRDATA::CWinLDAPAdaptor::Connect: SSL successfully enabled
[06/16/2015 09:21:47:870] ERR: DIRDATA: [0b80] DIRDATA::CWinLDAPAdaptor::Connect: Error cannot connect to LDAP server ldap-cs.XXXXXXXXXXX.com:XXXXX because Comparación falsa, Error code = 5”

[salav]

Another point:

Does oneX communicator v6.2.6 support TLS conexion with LDAP??

in 6.25 I got to connect but with TCP not TLS

[salav]

Is there any way to detect errors in wireshark?

Has anyone suffer this kind of problem?

[fazil3]

One-X Communicator uses standard Win LDAP library to communicate with LDAP server and not the secure LDAP.
Below is an excerpt from Administering Avaya one-X® Communicator guide:

LDAP Search Directory-related paramters:
- SP_DIRSRVR: The IP address or FQDN of the LDAP directory server name or address.
- SP_DIRSRVRPORT: the TCP port number of the LDAP directory server: The default is 389
- SP_DIRTOPDN: The topmost distinguished name in the directory.
- SP_DIRTYPE: The directory type: The value should be in capital letters, for example, ACTIVEDIRECTORY, DOMINO, or NOVELL. This parameter is Avaya one-X Communicator-specific. You must enter this parameter in the file manually.

Typically the port numbers for LDAP connection are:
- 389 for unsecure LDAP connections
- 636 for secure LDAP connections
- 3268 for Microsoft unsecure LDAP connections
- 3269 for Microsoft secure LDAP connections

In conclusion, it may work but LDAPSecure i believe it is not tested. Not sure if the latest releases or upcoming ones have this resolved.