If you want to add additional directory search locations that the Call Bridge will consult when Cisco Meeting App users perform searches, follow these steps:
- Use an app such as Chrome Postman to login to the Meeting Server API.
- Create an LDAP server entry in the Meeting Server. The figure below shows an ldapserver entry being POSTed to the Meeting Server at URL 192.168.6.25. The entry is for the LDAP server at URL 192.168.1.10, authorization information is provided.
This step provides the necessary information to authorize the Callbridge to access the LDAP server.
- Use GET to obtain the ID of the LDAP server entry created in step 2.
-
Create a DirectorySearchLocation by POSTing the LDAP server ID from step 3. The DirectorySearchLocation settings define the behavior of searching the directory. Ensure you set the data format to raw.
-
Use GET to obtain the ID of the Directory Search Location created in step 4.
-
Use PUT to edit the DirectorySearchLocation. Add the DirectorySearchLocation ID in the PUT URL and provide the detailed information about baseDN and filterFormat etc. Make sure that you set the data format to raw. For example:
PUT: https://192.168.6.25/api/v1/DirectorySearchLocations/4ff1804c-322b-4efa-8799-3136167ac53b
baseDn=OU=contacts,DC=example,DC=com&filterformat=cn=*$1*&firstname=givenname&lastname=sn&displayname=cn&sip=mail
-
Check that the configuration of the DirectorySearchLocation is as you expected.
For a detailed description of all parameters and response elements, see the section on External Directory Search Locations in the API Reference guide.
- Last update:
- 21-May-2019
- FAQ ID:
- 1194