Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0+ : Multi-tenancy considerations
7
2 Suggested Procedure
To provide multi-tenancy, follow these steps. The
provides an example.
1. Set up your tenant table using the API POST operation for creating tenants (see the API
Reference).
2. Set up the LDAP Servers, LDAP Mappings and LDAP Sources using the API.
l
LDAP Server configuration provides location and authentication, and is independent of
multi-tenancy. Equally multi-tenancy does not necessarily require more than one LDAP
Server if sub-OUs or subdomains are associated with a particular tenant; clearly, the
LDAP Source configuration must be configured appropriately
multi-tenancy. Equally multi-tenancy does not necessarily require more than one LDAP
Server if sub-OUs or subdomains are associated with a particular tenant; clearly, the
LDAP Source configuration must be configured appropriately
l
LDAP Mapping configuration defines the form of user account names created on
synchronization and is independent of multi-tenancy. If the optional cospaceUriMapping,
cospaceNameMapping and cospaceCallIdMapping API parameters are provided, then a
space will be created for every user who is created during synchronization. This very
powerful functionality is described in the API Reference guide.
synchronization and is independent of multi-tenancy. If the optional cospaceUriMapping,
cospaceNameMapping and cospaceCallIdMapping API parameters are provided, then a
space will be created for every user who is created during synchronization. This very
powerful functionality is described in the API Reference guide.
l
LDAP Source configuration defines which LDAP Source and LDAP mapping to use, the
set of Active Directory or OpenSSL users to consider for import and the filter pattern to
apply in order to decide whether to import individual users. LDAP Sources can be
associated with a tenant – and therefore the API POST operation may need to contain a
tenant id parameter if you are using multi-tenancy.
set of Active Directory or OpenSSL users to consider for import and the filter pattern to
apply in order to decide whether to import individual users. LDAP Sources can be
associated with a tenant – and therefore the API POST operation may need to contain a
tenant id parameter if you are using multi-tenancy.
Note: Each user and space must be able to be dialed; that is, requires a unique URI.
Therefore ensure that your LDAP Servers, LDAP Mappings and LDAP Sources are set up
to make this happen.
Therefore ensure that your LDAP Servers, LDAP Mappings and LDAP Sources are set up
to make this happen.
3. Synchronize LDAP sources, either through the API (recommended) or Web Admin
Interface:
l
POST operation on the "/ldapSyncs" node. See the API Reference for details. If the
synchronization completed successfully, the response includes a "Location" of the
form "/api/v1/ldapSyncs/<LDAPsync ID>”.
synchronization completed successfully, the response includes a "Location" of the
form "/api/v1/ldapSyncs/<LDAPsync ID>”.
l
Log in to the Web Admin Interface, go to Configuration > Active Directory and click
Sync now. Check that the synchronization completed successfully. For example,
check the syslog to verify that the process completed without errors and check the
Status > Users page in the Web Admin Interface to ensure that user names are as
intended.
Sync now. Check that the synchronization completed successfully. For example,
check the syslog to verify that the process completed without errors and check the
Status > Users page in the Web Admin Interface to ensure that user names are as
intended.
4. If you are using the Cisco Meeting App, check that spaces are set up as expected.
2 Suggested Procedure