WEBVTT

00:00:00.000 --> 00:00:03.430 align:middle line:90%


00:00:03.430 --> 00:00:04.900 align:middle line:90%
[ELECTRICAL PULSES]

00:00:04.900 --> 00:00:07.840 align:middle line:90%
[AUDIO LOGO]

00:00:07.840 --> 00:00:09.810 align:middle line:90%


00:00:09.810 --> 00:00:12.480 align:middle line:90%
Hello, and welcome to INE.

00:00:12.480 --> 00:00:15.540 align:middle line:84%
Today, in this video, we
would look at section 6, CMS,

00:00:15.540 --> 00:00:17.820 align:middle line:90%
basically, task 6.2.

00:00:17.820 --> 00:00:20.860 align:middle line:84%
Now, here in this task,
we have a requirement,

00:00:20.860 --> 00:00:26.910 align:middle line:84%
which says we need to use the
API to sync HQ users to CMS

00:00:26.910 --> 00:00:29.920 align:middle line:90%
and generate a coSpace for them.

00:00:29.920 --> 00:00:32.790 align:middle line:84%
We need to use the administrator
credentials to authenticate

00:00:32.790 --> 00:00:34.860 align:middle line:90%
against the AD server.

00:00:34.860 --> 00:00:39.510 align:middle line:84%
The AD server addresses
hq-internal-dash-dns.ine.com

00:00:39.510 --> 00:00:41.490 align:middle line:90%
on port 389.

00:00:41.490 --> 00:00:44.640 align:middle line:84%
Use the below information
for building the coSpaces.

00:00:44.640 --> 00:00:50.834 align:middle line:84%
The baseDn would be all
OU=hq, DC=ine, and DC=com.

00:00:50.834 --> 00:00:54.000 align:middle line:84%
LDAP server addresses
hq-intern-dns.ine.com.

00:00:54.000 --> 00:00:56.610 align:middle line:90%


00:00:56.610 --> 00:00:59.400 align:middle line:84%
The username password to
connect to the LDAP server

00:00:59.400 --> 00:01:01.890 align:middle line:84%
is going to be
administrator@ine.com,

00:01:01.890 --> 00:01:06.150 align:middle line:84%
and the password is going
to be C1sc0123!, where

00:01:06.150 --> 00:01:07.740 align:middle line:90%
C is uppercase.

00:01:07.740 --> 00:01:10.410 align:middle line:84%
The coSpace you are
mapping should be

00:01:10.410 --> 00:01:13.060 align:middle line:90%
based on the account name.join.

00:01:13.060 --> 00:01:17.940 align:middle line:84%
So let's say, if the username
is hq1, it should be hq1.join.

00:01:17.940 --> 00:01:22.440 align:middle line:84%
The coSpace secondly
you are mapping

00:01:22.440 --> 00:01:26.670 align:middle line:84%
should again be based on the
hostname or the username.meet.

00:01:26.670 --> 00:01:30.030 align:middle line:84%
And the coSpace call
ID mapping should

00:01:30.030 --> 00:01:31.780 align:middle line:84%
be based on the
telephone number,

00:01:31.780 --> 00:01:33.850 align:middle line:90%
so on the IP phone number.

00:01:33.850 --> 00:01:37.780 align:middle line:84%
So let's quickly
go and build this.

00:01:37.780 --> 00:01:39.810 align:middle line:84%
So the first thing
what I'm going to do

00:01:39.810 --> 00:01:44.310 align:middle line:90%
is access my CMS via GUI.

00:01:44.310 --> 00:01:47.170 align:middle line:84%
If you remember in
the earlier video,

00:01:47.170 --> 00:01:49.800 align:middle line:84%
we had configured the
CMS with web admin

00:01:49.800 --> 00:01:54.490 align:middle line:84%
so that we can access the
GUI through the jaba machine.

00:01:54.490 --> 00:01:55.800 align:middle line:90%
So let's quickly go and access.

00:01:55.800 --> 00:01:59.340 align:middle line:84%
Now, I could go and
configure LDAP using the GUI.

00:01:59.340 --> 00:02:03.270 align:middle line:84%
However, because my question
states that I need to use API,

00:02:03.270 --> 00:02:05.760 align:middle line:84%
I would have to do
it through the API.

00:02:05.760 --> 00:02:07.500 align:middle line:90%
I cannot do it through the GUI.

00:02:07.500 --> 00:02:11.700 align:middle line:84%
However, let's just quickly
go and access the CMS via GUI

00:02:11.700 --> 00:02:14.910 align:middle line:84%
and see if we have any
coSpaces preconfigured.

00:02:14.910 --> 00:02:17.260 align:middle line:90%
Let's go and do that.

00:02:17.260 --> 00:02:21.730 align:middle line:84%
So I'm going to go back
to my jaba machine,

00:02:21.730 --> 00:02:29.530 align:middle line:84%
and let's open up Firefox,
and let's access CMS.

00:02:29.530 --> 00:02:45.550 align:middle line:90%


00:02:45.550 --> 00:02:49.700 align:middle line:84%
Let's log in using
the credentials.

00:02:49.700 --> 00:02:52.190 align:middle line:84%
Now, if I go back
to status and users,

00:02:52.190 --> 00:02:53.690 align:middle line:84%
you would see that,
as of right now,

00:02:53.690 --> 00:02:56.530 align:middle line:84%
I don't have any users
because the only thing we

00:02:56.530 --> 00:03:00.310 align:middle line:84%
did in the earlier video
was basic integration where

00:03:00.310 --> 00:03:04.480 align:middle line:84%
we configure the call
bridge, the XMPP.

00:03:04.480 --> 00:03:07.240 align:middle line:84%
We made the connection between
the call bridge and XMPP,

00:03:07.240 --> 00:03:09.280 align:middle line:90%
and then we enabled web admin.

00:03:09.280 --> 00:03:10.690 align:middle line:90%
So I don't have any users.

00:03:10.690 --> 00:03:14.110 align:middle line:84%
If I go back to spaces, I
don't have any coSpaces.

00:03:14.110 --> 00:03:16.720 align:middle line:84%
If I go back to LDAP
Active Directory,

00:03:16.720 --> 00:03:19.960 align:middle line:84%
I have not configured
Active Directory or LDAP

00:03:19.960 --> 00:03:21.160 align:middle line:90%
using the GUI.

00:03:21.160 --> 00:03:26.020 align:middle line:84%
So I am going to use the API to
actually configure all of this.

00:03:26.020 --> 00:03:28.300 align:middle line:84%
Now, obviously, it's
going to be difficult

00:03:28.300 --> 00:03:33.220 align:middle line:84%
for you to remember how
to do it using the API.

00:03:33.220 --> 00:03:36.370 align:middle line:84%
So it's always better
to go to the API guide

00:03:36.370 --> 00:03:40.990 align:middle line:84%
and follow the steps
through the API guide.

00:03:40.990 --> 00:03:44.020 align:middle line:84%
Now, to access that
in the lab exam,

00:03:44.020 --> 00:03:57.220 align:middle line:84%
all you have to do is go to
www.cisco.com/go/meetingserver.

00:03:57.220 --> 00:03:59.740 align:middle line:84%
And you can directly type
this URL in the lab exam,

00:03:59.740 --> 00:04:04.440 align:middle line:84%
and you would be able to reach
the meeting server web page.

00:04:04.440 --> 00:04:06.270 align:middle line:90%
Again, that's going to be--

00:04:06.270 --> 00:04:08.280 align:middle line:84%
it shouldn't be from
the jaba machine

00:04:08.280 --> 00:04:10.030 align:middle line:84%
because that doesn't
have internet access.

00:04:10.030 --> 00:04:11.380 align:middle line:90%
So do it from your machine.

00:04:11.380 --> 00:04:18.829 align:middle line:84%
So go back to
www.cisco.com/go/meetingserver.

00:04:18.829 --> 00:04:26.600 align:middle line:84%
Scroll all the way down
to technical support.

00:04:26.600 --> 00:04:33.500 align:middle line:84%
Go down to documentation, and
scroll down to configuration.

00:04:33.500 --> 00:04:37.850 align:middle line:84%
And here, under
programming guides,

00:04:37.850 --> 00:04:42.290 align:middle line:84%
scroll down to View all
Types of Documentation.

00:04:42.290 --> 00:04:45.390 align:middle line:84%
And here you will
see an API guide.

00:04:45.390 --> 00:04:48.260 align:middle line:84%
So once you click
on that, you should

00:04:48.260 --> 00:04:49.520 align:middle line:90%
see the list of API guides.

00:04:49.520 --> 00:04:51.770 align:middle line:84%
So again, this depends on
the different versions.

00:04:51.770 --> 00:04:54.270 align:middle line:84%
It doesn't really matter
which version you choose.

00:04:54.270 --> 00:04:57.260 align:middle line:84%
Just make sure you choose the
version which is above the one

00:04:57.260 --> 00:04:59.280 align:middle line:90%
that your CMS is using.

00:04:59.280 --> 00:05:02.880 align:middle line:84%
So I'm just going to choose
any one, let's say, 3.2.

00:05:02.880 --> 00:05:07.500 align:middle line:90%
And this opens up my API guide.

00:05:07.500 --> 00:05:10.590 align:middle line:84%
And here, what
I'm going to do is

00:05:10.590 --> 00:05:18.090 align:middle line:90%
I will search for LDAP methods.

00:05:18.090 --> 00:05:20.790 align:middle line:84%
Now, the thing is
that what we need--

00:05:20.790 --> 00:05:22.140 align:middle line:90%
why do we need LDAP methods?

00:05:22.140 --> 00:05:25.020 align:middle line:84%
For you to import
the users from LDAP

00:05:25.020 --> 00:05:27.780 align:middle line:84%
and create coSpaces for
them, the first thing

00:05:27.780 --> 00:05:32.040 align:middle line:84%
you need to define is who is the
LDAP server, on what criteria

00:05:32.040 --> 00:05:36.760 align:middle line:84%
you're going to match the user's
based from the LDAP server,

00:05:36.760 --> 00:05:38.880 align:middle line:90%
so basically your jid mappings.

00:05:38.880 --> 00:05:41.430 align:middle line:84%
And then you're going
to create the coSpaces.

00:05:41.430 --> 00:05:43.030 align:middle line:90%
So search for LDAP methods.

00:05:43.030 --> 00:05:51.670 align:middle line:90%


00:05:51.670 --> 00:05:53.410 align:middle line:90%
It should give me--

00:05:53.410 --> 00:05:55.360 align:middle line:90%
let's scroll down.

00:05:55.360 --> 00:05:56.990 align:middle line:90%
It's not allowing me to search.

00:05:56.990 --> 00:06:00.520 align:middle line:84%
So let's scroll down
to LDAP methods.

00:06:00.520 --> 00:06:02.305 align:middle line:84%
It should be
somewhere down here.

00:06:02.305 --> 00:06:07.310 align:middle line:90%


00:06:07.310 --> 00:06:09.830 align:middle line:90%
LDAP methods, which is page 242.

00:06:09.830 --> 00:06:11.850 align:middle line:90%
So let's go to that page.

00:06:11.850 --> 00:06:17.730 align:middle line:84%
And here, what we will
do is follow the steps.

00:06:17.730 --> 00:06:20.430 align:middle line:90%
So we will start with 11.1.

00:06:20.430 --> 00:06:23.810 align:middle line:84%
So 11.1.1 says retrieving
the LDAP servers.

00:06:23.810 --> 00:06:25.560 align:middle line:84%
We haven't really
configured LDAP servers,

00:06:25.560 --> 00:06:28.320 align:middle line:84%
so there's no point of
retrieving any LDAP server.

00:06:28.320 --> 00:06:32.870 align:middle line:84%
So I skip that step
and go to 11.1.2,

00:06:32.870 --> 00:06:35.940 align:middle line:84%
which is Adding or
Modifying an LDAP Server.

00:06:35.940 --> 00:06:39.170 align:middle line:84%
Now, obviously, I have
to do this through API,

00:06:39.170 --> 00:06:42.380 align:middle line:84%
so I need Postman
to connect to CMS

00:06:42.380 --> 00:06:44.370 align:middle line:90%
and configure the LDAP server.

00:06:44.370 --> 00:06:47.780 align:middle line:84%
So I'm going to go
back to my jaba machine

00:06:47.780 --> 00:06:49.865 align:middle line:90%
and open up Postman.

00:06:49.865 --> 00:07:05.270 align:middle line:90%


00:07:05.270 --> 00:07:08.090 align:middle line:84%
Now, once Postman opens
up, the first thing

00:07:08.090 --> 00:07:11.990 align:middle line:84%
that I want you to do is
verify if SSL certificate

00:07:11.990 --> 00:07:15.020 align:middle line:84%
authentication is
disabled because this jaba

00:07:15.020 --> 00:07:16.640 align:middle line:84%
machine, which has
Postman installed,

00:07:16.640 --> 00:07:18.710 align:middle line:84%
does not have the
certificate for CMS.

00:07:18.710 --> 00:07:20.840 align:middle line:84%
And CMS is using a
self-signed cert.

00:07:20.840 --> 00:07:23.910 align:middle line:84%
It's not going to trust
the connection to CMS.

00:07:23.910 --> 00:07:30.470 align:middle line:84%
So what I would suggest is
go to File, go to Settings,

00:07:30.470 --> 00:07:34.470 align:middle line:84%
and ensure SSL certificate
verification is disabled.

00:07:34.470 --> 00:07:36.230 align:middle line:90%
So disable that.

00:07:36.230 --> 00:07:42.710 align:middle line:84%
Then you can close this tab
and click on New HTTP request.

00:07:42.710 --> 00:07:45.510 align:middle line:90%
This opens up a new tab for you.

00:07:45.510 --> 00:07:49.620 align:middle line:84%
Now, here you would
go to authorization

00:07:49.620 --> 00:07:52.950 align:middle line:84%
and choose the
type as basic art.

00:07:52.950 --> 00:07:57.130 align:middle line:84%
And provide the username
password for connecting to CMS.

00:07:57.130 --> 00:08:00.390 align:middle line:84%
So the username
was administrator,

00:08:00.390 --> 00:08:05.430 align:middle line:90%
and password is C1sc0123!.

00:08:05.430 --> 00:08:09.600 align:middle line:84%
That's a username password
to connect to a CMS.

00:08:09.600 --> 00:08:13.050 align:middle line:84%
Next, you would go and
change this to post.

00:08:13.050 --> 00:08:15.630 align:middle line:90%
And here you would type the URL.

00:08:15.630 --> 00:08:18.360 align:middle line:84%
Now, the first part
of the URL always

00:08:18.360 --> 00:08:20.160 align:middle line:90%
remains the same, always.

00:08:20.160 --> 00:08:22.570 align:middle line:90%
It's always the same.

00:08:22.570 --> 00:08:25.020 align:middle line:84%
The last part of
the URL is what we

00:08:25.020 --> 00:08:27.040 align:middle line:90%
would take from the API guide.

00:08:27.040 --> 00:08:30.510 align:middle line:84%
So the first part
is going to be--

00:08:30.510 --> 00:08:37.650 align:middle line:84%
If I actually look at the API
guide, the only thing the API

00:08:37.650 --> 00:08:39.750 align:middle line:84%
guide tells me to
add in LDAP server,

00:08:39.750 --> 00:08:42.690 align:middle line:84%
I need to have this
part LDAP servers.

00:08:42.690 --> 00:08:45.390 align:middle line:84%
But I need to first put
the first part of the URL.

00:08:45.390 --> 00:08:53.901 align:middle line:84%
So that's going to be
https://hq-cms.ine.com

00:08:53.901 --> 00:08:55.614 align:middle line:90%
and /api/v1/--

00:08:55.614 --> 00:08:58.590 align:middle line:90%


00:08:58.590 --> 00:09:03.130 align:middle line:84%
so this part of the URL
always remains the same.

00:09:03.130 --> 00:09:04.890 align:middle line:84%
The second part of
the URL is going

00:09:04.890 --> 00:09:10.350 align:middle line:84%
to be from the API guide, which
is going to be LDAP servers.

00:09:10.350 --> 00:09:11.610 align:middle line:90%
So /LDAPservers.

00:09:11.610 --> 00:09:14.640 align:middle line:90%


00:09:14.640 --> 00:09:17.610 align:middle line:90%
Now, here I would go to body.

00:09:17.610 --> 00:09:21.870 align:middle line:90%
choose x-www-form--urlencoded.

00:09:21.870 --> 00:09:25.110 align:middle line:84%
And now, I will provide
the key and the values

00:09:25.110 --> 00:09:26.340 align:middle line:90%
based on the guide.

00:09:26.340 --> 00:09:27.810 align:middle line:90%
So what do we need?

00:09:27.810 --> 00:09:29.770 align:middle line:90%
I need the server's address.

00:09:29.770 --> 00:09:31.813 align:middle line:84%
So I would just put the
minimum requirements.

00:09:31.813 --> 00:09:33.480 align:middle line:84%
If you look at the
minimum requirements,

00:09:33.480 --> 00:09:35.550 align:middle line:84%
it says addresses
minimum requirement,

00:09:35.550 --> 00:09:37.170 align:middle line:84%
port numbers
minimum requirement,

00:09:37.170 --> 00:09:39.510 align:middle line:84%
and secure is
minimum requirement.

00:09:39.510 --> 00:09:41.460 align:middle line:84%
I will also put the
username password

00:09:41.460 --> 00:09:43.180 align:middle line:84%
for connecting to
the LDAP server.

00:09:43.180 --> 00:09:44.980 align:middle line:90%
So let's go and add all of this.

00:09:44.980 --> 00:09:50.850 align:middle line:84%
So first one is going to
be address, A-D-D-R-E-S-S,

00:09:50.850 --> 00:09:58.620 align:middle line:84%
and the value is going to be
hq-internal-dns.ine.com as per

00:09:58.620 --> 00:10:00.530 align:middle line:90%
the question.

00:10:00.530 --> 00:10:08.120 align:middle line:84%
Port number is going to be
389 to connect to LDAP server.

00:10:08.120 --> 00:10:11.330 align:middle line:84%
Username to connect
to the LDAP server

00:10:11.330 --> 00:10:14.030 align:middle line:84%
is going to be
administrator@ine.com.

00:10:14.030 --> 00:10:16.950 align:middle line:90%


00:10:16.950 --> 00:10:24.210 align:middle line:84%
Password is going to
be C1sc0123!, where

00:10:24.210 --> 00:10:25.620 align:middle line:90%
C is uppercase.

00:10:25.620 --> 00:10:29.430 align:middle line:84%
And lastly, secure
is going to be--

00:10:29.430 --> 00:10:30.780 align:middle line:90%
let's go back to the document.

00:10:30.780 --> 00:10:32.800 align:middle line:90%
Secure says, true or false.

00:10:32.800 --> 00:10:34.620 align:middle line:90%
So if you want to make a--

00:10:34.620 --> 00:10:37.500 align:middle line:84%
if you set it to true, it's
going to make a TLS connection

00:10:37.500 --> 00:10:38.370 align:middle line:90%
to the LDAP server.

00:10:38.370 --> 00:10:41.590 align:middle line:84%
We haven't really defined
certs on the LDAP server.

00:10:41.590 --> 00:10:44.500 align:middle line:90%
So we should set this to false.

00:10:44.500 --> 00:10:46.350 align:middle line:90%
So let's set this to false.

00:10:46.350 --> 00:10:49.420 align:middle line:90%


00:10:49.420 --> 00:10:49.940 align:middle line:90%
That's it.

00:10:49.940 --> 00:10:51.100 align:middle line:90%
That's all we need.

00:10:51.100 --> 00:10:53.750 align:middle line:84%
And now, I would
send this to CMS.

00:10:53.750 --> 00:10:55.540 align:middle line:84%
So this would send
the information,

00:10:55.540 --> 00:10:58.730 align:middle line:84%
all this information to CMS
that this is your LDAP server.

00:10:58.730 --> 00:10:59.900 align:middle line:90%
How do you connect to it?

00:10:59.900 --> 00:11:02.260 align:middle line:84%
The port number, the username,
the password, and it's

00:11:02.260 --> 00:11:04.550 align:middle line:90%
not a TLS-based connection.

00:11:04.550 --> 00:11:06.370 align:middle line:90%
So let's do a send.

00:11:06.370 --> 00:11:09.250 align:middle line:90%
I should see a 200 OK.

00:11:09.250 --> 00:11:13.940 align:middle line:84%
And now, you should
do a get and do a send

00:11:13.940 --> 00:11:16.180 align:middle line:84%
so that we get the ID
of your LDAP server.

00:11:16.180 --> 00:11:17.440 align:middle line:90%
We need this ID.

00:11:17.440 --> 00:11:18.670 align:middle line:90%
The ID is here.

00:11:18.670 --> 00:11:19.900 align:middle line:90%
We need this ID.

00:11:19.900 --> 00:11:23.800 align:middle line:84%
So keep this page
as it is, and do

00:11:23.800 --> 00:11:26.780 align:middle line:90%
a duplicate for the next step.

00:11:26.780 --> 00:11:29.300 align:middle line:90%
So duplicate this tab.

00:11:29.300 --> 00:11:31.600 align:middle line:84%
Do not modify anything
on this tab anymore.

00:11:31.600 --> 00:11:33.220 align:middle line:90%
This is your LDAP server.

00:11:33.220 --> 00:11:35.200 align:middle line:90%
Go back to the second page.

00:11:35.200 --> 00:11:38.470 align:middle line:84%
And now, we would change
this to POST again.

00:11:38.470 --> 00:11:42.890 align:middle line:90%
And we would go back to Body.

00:11:42.890 --> 00:11:48.180 align:middle line:84%
And here, what I'm
going to do is--

00:11:48.180 --> 00:11:50.010 align:middle line:90%
let me go back and check--

00:11:50.010 --> 00:11:52.170 align:middle line:90%
go back to Body.

00:11:52.170 --> 00:11:54.935 align:middle line:84%
And let's go back to
our documentation.

00:11:54.935 --> 00:11:57.060 align:middle line:84%
So step number one, which
is adding the LDAP server

00:11:57.060 --> 00:11:58.950 align:middle line:90%
was done, 11.1.2.

00:11:58.950 --> 00:11:59.790 align:middle line:90%
Let's scroll down.

00:11:59.790 --> 00:12:01.560 align:middle line:90%
Retrieving was done.

00:12:01.560 --> 00:12:06.100 align:middle line:84%
Now, we go define 11.2.1,
which is LDAP mapping.

00:12:06.100 --> 00:12:08.550 align:middle line:84%
So LDAP mapping is
from the LDAP server.

00:12:08.550 --> 00:12:10.740 align:middle line:84%
How should I get--
what user should I

00:12:10.740 --> 00:12:13.290 align:middle line:84%
get because I may have
thousands of users, users

00:12:13.290 --> 00:12:16.290 align:middle line:84%
who belong to sales department,
users who belong to maybe

00:12:16.290 --> 00:12:19.440 align:middle line:84%
the organization HQ or
organization site B.

00:12:19.440 --> 00:12:20.700 align:middle line:90%
I may have multiple users.

00:12:20.700 --> 00:12:22.570 align:middle line:90%
I only want specific users.

00:12:22.570 --> 00:12:24.750 align:middle line:84%
So I would define
the LDAP mapping

00:12:24.750 --> 00:12:27.970 align:middle line:90%
and define the coSpaces also.

00:12:27.970 --> 00:12:31.860 align:middle line:84%
So for LDAP mapping, the
URL is LDAP mappings.

00:12:31.860 --> 00:12:33.270 align:middle line:90%
So go back here.

00:12:33.270 --> 00:12:37.530 align:middle line:84%
Change the POST on the
second tab that we created,

00:12:37.530 --> 00:12:38.700 align:middle line:90%
that we duplicated.

00:12:38.700 --> 00:12:43.130 align:middle line:90%
Change this to LDAP mappings.

00:12:43.130 --> 00:12:45.750 align:middle line:84%
And now, we specify
all the parameters.

00:12:45.750 --> 00:12:51.600 align:middle line:84%
So the first parameter for
LDAP mapping was jid mapping.

00:12:51.600 --> 00:12:57.320 align:middle line:84%
So jid mapping, which you
can see in the documentation,

00:12:57.320 --> 00:12:59.240 align:middle line:90%
it is jid mapping.

00:12:59.240 --> 00:13:03.650 align:middle line:84%
And the name-- the
mapping would be based

00:13:03.650 --> 00:13:06.860 align:middle line:90%
on the username at ine.com.

00:13:06.860 --> 00:13:13.170 align:middle line:84%
So any user that has, let's say,
hq1@ine.com would be mapped.

00:13:13.170 --> 00:13:18.612 align:middle line:84%
So jig mapping would be based
on $sAMAccountName$@ine.com.

00:13:18.612 --> 00:13:30.030 align:middle line:90%


00:13:30.030 --> 00:13:32.970 align:middle line:84%
So if I see this, where
did I get this value from?

00:13:32.970 --> 00:13:34.350 align:middle line:84%
If you look at
the documentation,

00:13:34.350 --> 00:13:36.000 align:middle line:90%
it is right here.

00:13:36.000 --> 00:13:39.690 align:middle line:84%
Just change the
example.com to ine.com.

00:13:39.690 --> 00:13:44.590 align:middle line:84%
The next thing that I
need is name mapping.

00:13:44.590 --> 00:13:47.620 align:middle line:90%
How do I want to map the users?

00:13:47.620 --> 00:13:50.070 align:middle line:84%
So when I create the coSpaces,
what should be their name?

00:13:50.070 --> 00:13:52.300 align:middle line:84%
The name would be based
on their common name.

00:13:52.300 --> 00:13:56.760 align:middle line:84%
So again, you can see here
the value is [? $cn$. ?] So

00:13:56.760 --> 00:14:00.570 align:middle line:84%
let's go back here change the
second one to nameMapping.

00:14:00.570 --> 00:14:03.090 align:middle line:90%


00:14:03.090 --> 00:14:05.670 align:middle line:90%
And this would be $cn$.

00:14:05.670 --> 00:14:08.820 align:middle line:90%


00:14:08.820 --> 00:14:14.630 align:middle line:90%
The third one is cdrTagMapping.

00:14:14.630 --> 00:14:17.310 align:middle line:84%
Now, if you don't want to
define this, it's optional.

00:14:17.310 --> 00:14:19.730 align:middle line:84%
You don't need to define
the cdr Tag Mapping.

00:14:19.730 --> 00:14:22.370 align:middle line:84%
Authentication
mapping is mandatory.

00:14:22.370 --> 00:14:25.290 align:middle line:84%
So how are you going to
authenticate the user?

00:14:25.290 --> 00:14:29.210 align:middle line:84%
So authenticationidMapping,
let's put that.

00:14:29.210 --> 00:14:31.790 align:middle line:90%


00:14:31.790 --> 00:14:33.446 align:middle line:90%
AuthenticationidMapping.

00:14:33.446 --> 00:14:39.420 align:middle line:90%


00:14:39.420 --> 00:14:42.048 align:middle line:90%
That's going to be based on--

00:14:42.048 --> 00:14:42.840 align:middle line:90%
let's go back here.

00:14:42.840 --> 00:14:44.805 align:middle line:90%
It says $userPrincipleName$.

00:14:44.805 --> 00:14:48.870 align:middle line:90%


00:14:48.870 --> 00:14:51.070 align:middle line:90%
So $userPrincipleName$.

00:14:51.070 --> 00:15:06.590 align:middle line:90%


00:15:06.590 --> 00:15:10.730 align:middle line:84%
The next one after that
is-- let's scroll down--

00:15:10.730 --> 00:15:12.980 align:middle line:84%
coSpaceUriMapping
Now, my question

00:15:12.980 --> 00:15:15.530 align:middle line:84%
stated that the coSpace
Uri Mapping should

00:15:15.530 --> 00:15:19.740 align:middle line:90%
be based on account name.join.

00:15:19.740 --> 00:15:22.910 align:middle line:90%
So let's go back here.

00:15:22.910 --> 00:15:25.510 align:middle line:84%
So this would be
coSpaceUriMapping.

00:15:25.510 --> 00:15:29.740 align:middle line:90%


00:15:29.740 --> 00:15:31.600 align:middle line:90%
And this is going to be--

00:15:31.600 --> 00:15:34.590 align:middle line:90%


00:15:34.590 --> 00:15:36.060 align:middle line:90%
let's just copy this value.

00:15:36.060 --> 00:15:46.740 align:middle line:90%


00:15:46.740 --> 00:15:57.190 align:middle line:84%
So this is going to be
$sAMAccountName$.join,

00:15:57.190 --> 00:16:03.010 align:middle line:90%
I believe it was join, yes.

00:16:03.010 --> 00:16:12.830 align:middle line:84%
Then the second one, let's
copy this, paste this here.

00:16:12.830 --> 00:16:16.130 align:middle line:84%
The second one was
meet, the second rename.

00:16:16.130 --> 00:16:19.500 align:middle line:90%


00:16:19.500 --> 00:16:22.570 align:middle line:90%
And this name would be--

00:16:22.570 --> 00:16:23.745 align:middle line:90%
let's copy this from here.

00:16:23.745 --> 00:16:28.340 align:middle line:90%


00:16:28.340 --> 00:16:30.185 align:middle line:84%
This would be your
secondary name.

00:16:30.185 --> 00:16:33.090 align:middle line:90%


00:16:33.090 --> 00:16:34.910 align:middle line:90%
So SecondaryUriMapping name.

00:16:34.910 --> 00:16:36.390 align:middle line:90%
What else do we need?

00:16:36.390 --> 00:16:40.640 align:middle line:84%
We need the caller ID to
be based on the IP phone.

00:16:40.640 --> 00:16:43.632 align:middle line:90%
So go to coSpaceCallidMapping.

00:16:43.632 --> 00:16:48.470 align:middle line:90%


00:16:48.470 --> 00:16:50.720 align:middle line:90%
This would be based on $ipPhone.

00:16:50.720 --> 00:16:56.030 align:middle line:90%


00:16:56.030 --> 00:16:59.810 align:middle line:84%
Now, where do I get this
value IP phone from?

00:16:59.810 --> 00:17:01.730 align:middle line:84%
Again, my question
actually really says

00:17:01.730 --> 00:17:04.569 align:middle line:84%
that the value
should be ip Phone.

00:17:04.569 --> 00:17:06.510 align:middle line:84%
If I actually go back
to my LDAP server,

00:17:06.510 --> 00:17:09.750 align:middle line:84%
let's go and access
our LDAP server,

00:17:09.750 --> 00:17:15.359 align:middle line:84%
and let's actually
go to my LDAP user.

00:17:15.359 --> 00:17:16.520 align:middle line:90%
So go to Server Manager.

00:17:16.520 --> 00:17:21.030 align:middle line:90%


00:17:21.030 --> 00:17:23.010 align:middle line:90%
Go to Tools.

00:17:23.010 --> 00:17:24.944 align:middle line:90%
Go to ADSI Edit.

00:17:24.944 --> 00:17:29.300 align:middle line:90%


00:17:29.300 --> 00:17:33.590 align:middle line:84%
And if you see DC ine, DC
com, if you go to OU hq,

00:17:33.590 --> 00:17:34.880 align:middle line:90%
you'll see three users there.

00:17:34.880 --> 00:17:36.050 align:middle line:90%
Click on Tony Stark, right?

00:17:36.050 --> 00:17:37.340 align:middle line:90%
Click on Go to Properties.

00:17:37.340 --> 00:17:40.440 align:middle line:90%
You'll see all the attributes.

00:17:40.440 --> 00:17:42.840 align:middle line:84%
So if you look at it,
if you scroll down,

00:17:42.840 --> 00:17:45.650 align:middle line:84%
you would see an
attribute for ipPhone.

00:17:45.650 --> 00:17:49.290 align:middle line:84%
So it should be somewhere
here. ipPhone is here.

00:17:49.290 --> 00:17:51.830 align:middle line:84%
So this is the attribute
named the key name,

00:17:51.830 --> 00:17:55.080 align:middle line:90%
and this is the value.

00:17:55.080 --> 00:17:58.460 align:middle line:84%
So whatever his phone number
is, his ip Phone number

00:17:58.460 --> 00:18:01.120 align:middle line:84%
is, that's what's going to
show up in CMS in this coSpace.

00:18:01.120 --> 00:18:04.720 align:middle line:90%


00:18:04.720 --> 00:18:07.840 align:middle line:90%
Let's go back to jaba 1.

00:18:07.840 --> 00:18:11.270 align:middle line:90%
I believe this is enough.

00:18:11.270 --> 00:18:16.050 align:middle line:84%
Let's do a send
to LDAP mappings.

00:18:16.050 --> 00:18:17.430 align:middle line:90%
Now, let's do a get.

00:18:17.430 --> 00:18:20.100 align:middle line:84%
So now I have my LDAP
server configured,

00:18:20.100 --> 00:18:23.400 align:middle line:84%
and I have my LDAP
mapping configured.

00:18:23.400 --> 00:18:25.590 align:middle line:84%
So this tab is for
LDAP server, which

00:18:25.590 --> 00:18:28.350 align:middle line:90%
has the ID of LDAP server.

00:18:28.350 --> 00:18:30.660 align:middle line:84%
And this tab is the
LDAP mapping, which

00:18:30.660 --> 00:18:32.730 align:middle line:90%
has the ID for LDAP mapping.

00:18:32.730 --> 00:18:34.258 align:middle line:84%
Let's go back to
our documentation.

00:18:34.258 --> 00:18:35.550 align:middle line:90%
Let's see what's the next step.

00:18:35.550 --> 00:18:37.410 align:middle line:84%
Next step retrieving
the LDAP mapping.

00:18:37.410 --> 00:18:39.120 align:middle line:90%
We did that right now.

00:18:39.120 --> 00:18:40.260 align:middle line:90%
Let's scroll down.

00:18:40.260 --> 00:18:43.540 align:middle line:84%
Now, let's define
the LDAP source.

00:18:43.540 --> 00:18:47.910 align:middle line:84%
So in the LDAP
source the path is--

00:18:47.910 --> 00:18:49.230 align:middle line:90%
retrieving the LDAP sources.

00:18:49.230 --> 00:18:51.070 align:middle line:84%
We haven't configured
the LDAP sources yet,

00:18:51.070 --> 00:18:55.470 align:middle line:84%
so we will skip this spot and
go to adding an LDAP source.

00:18:55.470 --> 00:18:58.060 align:middle line:84%
It's a POST method
going to LDAP sources.

00:18:58.060 --> 00:18:59.460 align:middle line:90%
So let's go back here.

00:18:59.460 --> 00:19:06.810 align:middle line:84%
Let's duplicate this
one, duplicate tab.

00:19:06.810 --> 00:19:08.490 align:middle line:90%
Go to this third tab.

00:19:08.490 --> 00:19:10.830 align:middle line:90%
Change this to POST.

00:19:10.830 --> 00:19:12.776 align:middle line:90%
Change this to LDAP sources.

00:19:12.776 --> 00:19:17.100 align:middle line:90%


00:19:17.100 --> 00:19:19.780 align:middle line:90%
And go back to body.

00:19:19.780 --> 00:19:25.300 align:middle line:84%
And here we would put the
server's ID and the mapping

00:19:25.300 --> 00:19:30.600 align:middle line:84%
name and the baseDn
because on what criteria

00:19:30.600 --> 00:19:32.410 align:middle line:90%
I want to match the users.

00:19:32.410 --> 00:19:33.960 align:middle line:84%
I don't want to
import all the users.

00:19:33.960 --> 00:19:36.720 align:middle line:84%
I may have thousands of
users, which may belong

00:19:36.720 --> 00:19:37.800 align:middle line:90%
to different departments.

00:19:37.800 --> 00:19:42.150 align:middle line:84%
I only want users
that belong to OU hq.

00:19:42.150 --> 00:19:46.380 align:middle line:90%
So for this I would go to my--

00:19:46.380 --> 00:19:47.760 align:middle line:90%
back here.

00:19:47.760 --> 00:19:53.790 align:middle line:84%
And I'll change this
first one to server.

00:19:53.790 --> 00:19:55.270 align:middle line:90%
So who is my LDAP server?

00:19:55.270 --> 00:19:58.950 align:middle line:84%
So here, the value that
I would give inside this

00:19:58.950 --> 00:20:00.960 align:middle line:84%
is going to be going
back to the first step

00:20:00.960 --> 00:20:02.550 align:middle line:90%
where I have my LDAP server.

00:20:02.550 --> 00:20:04.720 align:middle line:90%
Take this ID.

00:20:04.720 --> 00:20:06.055 align:middle line:90%
So copy this ID.

00:20:06.055 --> 00:20:10.070 align:middle line:90%


00:20:10.070 --> 00:20:15.880 align:middle line:84%
Let's copy this, and go
back to your third tab

00:20:15.880 --> 00:20:17.635 align:middle line:90%
and put the server's ID here.

00:20:17.635 --> 00:20:20.260 align:middle line:90%


00:20:20.260 --> 00:20:23.680 align:middle line:84%
Then this one is
going to be mapping.

00:20:23.680 --> 00:20:27.360 align:middle line:84%
Take the mappings ID,
which is the second tab.

00:20:27.360 --> 00:20:28.130 align:middle line:90%
Copy the ID.

00:20:28.130 --> 00:20:34.070 align:middle line:90%


00:20:34.070 --> 00:20:38.225 align:middle line:84%
And go back to your third
tab and paste that there.

00:20:38.225 --> 00:20:44.030 align:middle line:90%


00:20:44.030 --> 00:20:49.850 align:middle line:84%
Then the next is going to
be, the third one was--

00:20:49.850 --> 00:20:51.590 align:middle line:84%
let me, in fact,
delete all of this.

00:20:51.590 --> 00:20:55.180 align:middle line:90%


00:20:55.180 --> 00:20:59.850 align:middle line:84%
So the third one is ask for
documentation is the base Dn.

00:20:59.850 --> 00:21:00.720 align:middle line:90%
I need base Dn.

00:21:00.720 --> 00:21:04.130 align:middle line:90%


00:21:04.130 --> 00:21:19.881 align:middle line:84%
So base Dn is going to be
based on OU=hq, DC=ine, DC=com.

00:21:19.881 --> 00:21:23.740 align:middle line:84%
And the last one I'm going
to put here is filter.

00:21:23.740 --> 00:21:25.080 align:middle line:90%
I need a filter.

00:21:25.080 --> 00:21:29.540 align:middle line:84%
If you look at the
requirements, filter

00:21:29.540 --> 00:21:33.870 align:middle line:84%
is something that I need to
match users based on something.

00:21:33.870 --> 00:21:38.420 align:middle line:84%
So all of my users, if you look
at the LDAP, all of my users

00:21:38.420 --> 00:21:39.560 align:middle line:90%
they have--

00:21:39.560 --> 00:21:46.290 align:middle line:84%
all my HQ users, they have
an email address defined.

00:21:46.290 --> 00:21:49.310 align:middle line:84%
I believe it's the
username@ine.com.

00:21:49.310 --> 00:21:53.280 align:middle line:84%
So I'm going to match
it based on this email.

00:21:53.280 --> 00:21:56.180 align:middle line:90%
So let's go back to jaba.

00:21:56.180 --> 00:22:01.520 align:middle line:84%
Filter is going to be based on
mail, which is equal to star.

00:22:01.520 --> 00:22:07.040 align:middle line:84%
So any user that has an email
address defined and which

00:22:07.040 --> 00:22:12.650 align:middle line:84%
belongs to the organization
hq, and DC ine and DC com, then

00:22:12.650 --> 00:22:15.980 align:middle line:84%
those users are going to be
imported from the server, whose

00:22:15.980 --> 00:22:17.660 align:middle line:90%
ID we have defined.

00:22:17.660 --> 00:22:20.870 align:middle line:84%
And the coSpaces names would
be based on the mapping ID

00:22:20.870 --> 00:22:22.590 align:middle line:90%
that we've defined.

00:22:22.590 --> 00:22:23.090 align:middle line:90%
That's it.

00:22:23.090 --> 00:22:24.410 align:middle line:90%
Let's go and send this.

00:22:24.410 --> 00:22:28.340 align:middle line:90%


00:22:28.340 --> 00:22:32.880 align:middle line:84%
Let's do a get, so we get the
ID of the server, of the source.

00:22:32.880 --> 00:22:33.980 align:middle line:90%
This is my ID.

00:22:33.980 --> 00:22:35.970 align:middle line:90%
Let's now do an LDP sync.

00:22:35.970 --> 00:22:38.490 align:middle line:84%
So let's do one
more duplicate tab.

00:22:38.490 --> 00:22:39.870 align:middle line:90%
This is the last step.

00:22:39.870 --> 00:22:42.710 align:middle line:84%
So we go back here,
change this to POST.

00:22:42.710 --> 00:22:47.320 align:middle line:84%
And this would
change to LDAP sync.

00:22:47.320 --> 00:22:49.820 align:middle line:84%
Again, if you go back to your
documentation and scroll down,

00:22:49.820 --> 00:22:52.220 align:middle line:90%
next step was a LDAP sync.

00:22:52.220 --> 00:22:54.590 align:middle line:90%
We need to do not retrieve.

00:22:54.590 --> 00:22:56.240 align:middle line:90%
We need to do a send.

00:22:56.240 --> 00:22:59.030 align:middle line:84%
So initiate an LDAP send
to download all the users

00:22:59.030 --> 00:23:00.650 align:middle line:90%
and create the coSpaces.

00:23:00.650 --> 00:23:03.020 align:middle line:90%
The name is ldapSyncs.

00:23:03.020 --> 00:23:03.980 align:middle line:90%
So let's go back here.

00:23:03.980 --> 00:23:07.980 align:middle line:84%
This would become
ldapSync, go back to body.

00:23:07.980 --> 00:23:12.200 align:middle line:90%
And here we would define--

00:23:12.200 --> 00:23:14.180 align:middle line:90%
let's look at the documentation.

00:23:14.180 --> 00:23:15.125 align:middle line:90%
ldapSource.

00:23:15.125 --> 00:23:17.660 align:middle line:90%


00:23:17.660 --> 00:23:20.050 align:middle line:90%
So let's delete all of this.

00:23:20.050 --> 00:23:20.908 align:middle line:90%
We don't need this.

00:23:20.908 --> 00:23:21.700 align:middle line:90%
We don't need this.

00:23:21.700 --> 00:23:22.780 align:middle line:90%
We just need two.

00:23:22.780 --> 00:23:26.840 align:middle line:84%
First, it's going
to be ldapSource.

00:23:26.840 --> 00:23:31.880 align:middle line:84%
So the ldapSource is going to
be the ID of your ldapSource,

00:23:31.880 --> 00:23:34.030 align:middle line:90%
which is a third tab here.

00:23:34.030 --> 00:23:35.725 align:middle line:90%
ldapSource, let's take this ID.

00:23:35.725 --> 00:23:40.560 align:middle line:90%


00:23:40.560 --> 00:23:44.085 align:middle line:84%
Go back to the fourth
tab, and let's paste that.

00:23:44.085 --> 00:23:47.370 align:middle line:90%


00:23:47.370 --> 00:23:53.560 align:middle line:84%
And this is going to be
remove when finished.

00:23:53.560 --> 00:23:56.160 align:middle line:90%


00:23:56.160 --> 00:23:57.860 align:middle line:90%
This would be set to false.

00:23:57.860 --> 00:24:02.290 align:middle line:90%


00:24:02.290 --> 00:24:06.030 align:middle line:84%
If I look back here, I have
the option of true and false.

00:24:06.030 --> 00:24:10.140 align:middle line:84%
True means the ldapSync
will, when it is finished,

00:24:10.140 --> 00:24:13.620 align:middle line:84%
be removed from the
system track list

00:24:13.620 --> 00:24:15.460 align:middle line:90%
and can no longer be queried.

00:24:15.460 --> 00:24:17.940 align:middle line:84%
So let's say, if you had
added some more users later,

00:24:17.940 --> 00:24:21.390 align:middle line:84%
we can always use the
same ldapSync retrieve

00:24:21.390 --> 00:24:22.530 align:middle line:90%
those new users.

00:24:22.530 --> 00:24:27.060 align:middle line:84%
But if you set it to
false, then the ldapSync

00:24:27.060 --> 00:24:29.290 align:middle line:90%
will persist in the system.

00:24:29.290 --> 00:24:31.320 align:middle line:90%
And you can reuse it later.

00:24:31.320 --> 00:24:32.740 align:middle line:84%
If you set it to
true, it's gone.

00:24:32.740 --> 00:24:34.200 align:middle line:90%
It's only a one-time execution.

00:24:34.200 --> 00:24:35.700 align:middle line:84%
So it's really up
to you whether you

00:24:35.700 --> 00:24:37.140 align:middle line:90%
want it to be false or true.

00:24:37.140 --> 00:24:42.800 align:middle line:84%
I'm going to set it to
false and do a send.

00:24:42.800 --> 00:24:44.930 align:middle line:84%
So once I've done
the ldapSync, let's

00:24:44.930 --> 00:24:48.840 align:middle line:84%
go back and do a get and see
if we downloaded any users.

00:24:48.840 --> 00:24:51.050 align:middle line:90%
Let's do a send.

00:24:51.050 --> 00:24:51.990 align:middle line:90%
So what do I see?

00:24:51.990 --> 00:24:53.750 align:middle line:84%
I see complete,
and I see a number

00:24:53.750 --> 00:24:58.280 align:middle line:84%
of users imported three, which
means my ldapSync is completed.

00:24:58.280 --> 00:25:02.780 align:middle line:84%
Let's now go back to--
let's minimize this Postman,

00:25:02.780 --> 00:25:09.800 align:middle line:90%
go back to your CMS GUI.

00:25:09.800 --> 00:25:13.130 align:middle line:84%
And now go to Status
and look at users.

00:25:13.130 --> 00:25:15.530 align:middle line:84%
You have three users
which were imported

00:25:15.530 --> 00:25:20.270 align:middle line:84%
from the HQ organization,
Tony Stark, HQ1, and HQ2.

00:25:20.270 --> 00:25:23.480 align:middle line:84%
Look at the email,
TonyStark@ine.com.

00:25:23.480 --> 00:25:26.720 align:middle line:84%
The XMPP ID is
Tony-Stark@ine.com.

00:25:26.720 --> 00:25:29.930 align:middle line:84%
And if I go to
Configuration spaces,

00:25:29.930 --> 00:25:33.890 align:middle line:84%
you would see the spaces
were created for them.

00:25:33.890 --> 00:25:41.450 align:middle line:84%
The spaces was HQ-1.join,
and TonyStark.join, HQ2.join.

00:25:41.450 --> 00:25:44.870 align:middle line:84%
And the secondary uri
name was HQ1.meet.

00:25:44.870 --> 00:25:49.190 align:middle line:84%
And the quality is
2001, 2003, 2002.

00:25:49.190 --> 00:25:51.680 align:middle line:90%
The name did not come.

00:25:51.680 --> 00:25:55.010 align:middle line:84%
Let's go back and
check if we required

00:25:55.010 --> 00:25:58.050 align:middle line:84%
the-- we didn't require
the name to be configured.

00:25:58.050 --> 00:26:01.850 align:middle line:84%
So if I actually
look back at my--

00:26:01.850 --> 00:26:07.790 align:middle line:84%
let's go back to my jaba Postman
and look at my jid mapping.

00:26:07.790 --> 00:26:13.795 align:middle line:84%
Maybe there was a mistake
in the name mapping.

00:26:13.795 --> 00:26:20.450 align:middle line:90%


00:26:20.450 --> 00:26:25.310 align:middle line:84%
It looks OK, so maybe
there was no common name

00:26:25.310 --> 00:26:26.500 align:middle line:90%
configured for the user.

00:26:26.500 --> 00:26:28.250 align:middle line:84%
So maybe that's why
the name did not come.

00:26:28.250 --> 00:26:29.090 align:middle line:90%
But that's OK.

00:26:29.090 --> 00:26:32.240 align:middle line:84%
The coSpaces were created
as per the requirements

00:26:32.240 --> 00:26:33.390 align:middle line:90%
of the question.

00:26:33.390 --> 00:26:38.660 align:middle line:84%
So you see, we basically used
an API to connect to CMS and ask

00:26:38.660 --> 00:26:41.870 align:middle line:84%
CMS to connect to LDAP,
download the users,

00:26:41.870 --> 00:26:46.820 align:middle line:84%
create coSpaces for them, create
a primary uri mapping name,

00:26:46.820 --> 00:26:50.690 align:middle line:84%
which is .join and .meet for
the secondary uri mapping name.

00:26:50.690 --> 00:26:54.950 align:middle line:84%
And the call ID was based
on their IP phone number.

00:26:54.950 --> 00:26:58.160 align:middle line:84%
With this, we've met all of
the requirements of the task.

00:26:58.160 --> 00:27:00.210 align:middle line:84%
I hope this video was
informative to you.

00:27:00.210 --> 00:27:02.500 align:middle line:90%
And thank you for watching.

00:27:02.500 --> 00:27:03.000 align:middle line:90%