Now the Westbound API, in spirit,
is very similar to the Eastbound API.
We're still talking about integrating applications
with our network.
But instead of integrating and sending data outbound,
we're now talking about integrating with other systems
and services within our own network.
So by the end of this Nugget, you're
going to understand how the Westbound
API can bring our infrastructure all together.
Get ready.
It's going to be fun.
Let's go!
Now for our final hurrah, we're going
to talk about what happens in the Westbound direction. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to talk about what happens in the Westbound direction.
But again, this is going to be an important one
to write in two directions here.
I'm going to write it in this way
because that's really what takes place.
Now what we're talking about when
we talk about the Westbound API is talking about integrating
our other services that take place
within the network with our controller.
This is things like these Cisco ICE line of products,
or Active Directory, or maybe an IPAM server.
Maybe it could be a NetFlow collector or a Syslog server, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Maybe it could be a NetFlow collector or a Syslog server,
or it's SNMP server.
Whatever the case is, if it provides some sort of service
within our network, this is where
we could integrate them together with our networking solution.
So maybe when a user is trying to get
authenticated into our network by connecting in ultimately
behind one of these Firepower devices,
maybe we want Firepower Management Center
to send this information to ICE to validate their information.
This is pretty common with things like RADIUS or TACACS.
And then from ICE here, it could be integrated WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then from ICE here, it could be integrated
into Active Directory, that communication taking place
with LDAP or Kerberos.
But the point is is that with the Westbound API,
we're trying to more seamlessly bring our network
and our servers and systems together into one solution
rather than having completely separated roles
within our infrastructure.
Obviously, Active Directory will still always
be Active Directory.
But wouldn't it be nice if Active Directory
worked and played nicely with our other services and systems?
Absolutely.
And that's what we're talking about when we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's what we're talking about when we
talk about the Westbound API.
So now with the end of our journey,
we see that the Northbound API is
where we communicate our policy intent
to the centralized networking solution.
Southbound is where that intent gets carried out
to the endpoint devices.
Eastbound is where we can send information out
to any other application that we want.
And westbound is where our servers and systems
and other networking services can
be integrated within the controller
that we're using now.
So that's been the journey through what an API does. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that's been the journey through what an API does.
I hope this has been informative for you.
And I'd like to thank you for viewing.