Configuring LDAP Users on Cisco Meeting Server via API

Introduction

This document describes configuration of LDAP (Lightweight Directory Access Protocol) on Cisco Meeting Server via API (Application Programming Interface). 

Prerequisites

PostMan App

Cisco Meeting Server (CMS)

Microsoft Active Directory

Requirements

There are no specific requirements for this document.

Components Used

Cisco Meeting Server

Microsoft Active Directory 

Background Information 

High level configuration flow to sync LDAP via API. 

Step 1. Configure /ldapServers parameter thru API as described below

1. LDAP server's address/port information
2. Username and password for accessing the server
3. Secure of non secure ldap.

Step 2 : Configure /ldapMappings parameter through API as described below

1. LDAP user properties objects to cms corresponding user objects 
2. Example cms user jid will map to $sAMAccountName$@domain.com on cms and etc.

Step 3: Configure /ldapSources parameters thru API as described below which to tie ldapServers and ldapMappings object.

Configure

Step 1. Configure /ldapServers

1. Send a POST for /ldapServers , which would create a ldapServer ID. Use unique /ldapServers ID for further configuration.
2. Response to POST would return in similar format <ldapServer id="7ca32cc4-389f-46f5-a1b0-0a468af291a4"> 
3. Capture below information to update LDAP Server ID per the CMS API Reference Guide
   
4. Sample POST Method with Parameters
   
5. Perform a GET to verify configured parameters

Step 2, Configure /ldapMappings 

1. Send a POST for /ldapMappings  to create a /ldapMappings ID. Use /ldapMappings ID and configure below parameters.
   
2. Capture below information to update LDAP Mapping ID per the CMS API Reference Guide
   
3. Configure below parameters for ldapMappings
4. Perform a GET to verify configured parameters.

Step 3. Configure /ldapsources 

1. Send a POST for /ldapsources to create a /ldapsources ID. Use /ldapsources ID and configure below parameters.
2. Capture below information to update LDAP Mapping ID per the CMS API Reference Guide
3. Configure below parameters for ldapSources
4. Perform a GET to verify configured parameters.
   

Configuration is complete. We can perform a full sync now.

Verify

Step 1. Send POST for /ldapSyncs from API and check event logs

Step 2. Check in event logs if sync is completed.

Step 3. Verify Users are synced from ldap source.

Troubleshoot

Verify API parameters and LDAP Attributes are accurate. 

Taking packet captures from call Bridge helps in isolating connectivity issues with LDAP.