Cisco Meeting Server - Secure LDAP (LDS)

[hogils53559]

Hi all

I am currently trying to deploy CMS (2.2.10) with user sync from ADLDS

From what i read online, LDS is just another LDAP server, which i think should be supported on CMS.

The problem is that LDS is using secure connection (636 - SSL), i can only read from API reference in CMS that it supports secure connection to LDAP server, but i am not too sure as to where i should configure the certificate needed to establish the secure connection to the ADLDS server

any help is appreciated.......

Best Regards,

Malvin Handerson

[R0g22]

CMS does support LDS and you can use either default non-secure port 389 or secure port 636 but it's recommended to use secure LDAP since the default LDAP bind does not protect the passwords.
Regarding secure LDAP, on the web admin, change the port to 636 and ensure that the "Secure Connection" box is checked. API is required if you need to configure multiple LDAP servers. Through web admin, you can configure only a single server.

[hogils53559]

Hi Nipun

i see the secure connection box that you mentioned, i was just comparing it to "CUCM integration to AD LDS" which require SSL connection between CUCM and AD LDS

in CUCM we can trust AD LDS certificate by uploading it in the CUCM OS Administration

but in CMS, do we need to import AD LDS certificate? and if it needs to, where do we specify the CMS to use the certificate during connection to AD LDS?

[R0g22]

I don’t believe you need any certs. I have this running in my lab without any certs and user import works fine.

[hogils53559]

Hi Nipun

thanks for your fast response

will try it out on my environment and get back to you if i have anymore enquiries

[4smacon]

Hi, the LDS and AD servers have a certificate in use for the Trust. During the CUCM configuration with LDS, you have to upload the certificate in order for the LDAP syncs to work.  Did we ever determine if the certificate too is required for the CMS LDAP integration?  If it is, you would just use the FTP server to place it on the server. However, I am wanting to determine if this was determined to be a definite need for the CMS LDAP configuration.