Welcome back. Now for our final coverage, our final topic will be on an instant access point. There is actually automation options available for you here as well. In order to access the REST API function on an Instant AP, you need to recognize that first of all, it's disabled by default on your instant access points. So you would need to go to the command line at the InstantAP and issue the command, allow-rest-API, and end commit apply your changes there. When you do, you're going to login to the master instance AP. There's a sample curl command where they did exactly that. They issued a curl to the whatever address was 4343. You might recognize that's the port number we use for our Aruba ALS 8 version, forward slash rest login and dash H. For the header content, we're going to expect JSON. The data we're going to supply to login will be the user, whatever that is, password, and then we can support dash insecure, and we'll get a status response here. The status message should include the SID or the session ID, and this session ID has to be used in all configurations with this cluster of instant APs. If you want to config or change something or do some monitoring, GIT commands, whatever, you would require this session ID. It's worth noting that this is for a cluster of access points. So only the master of that cluster, the one AP that runs the show there, is going to be the one that supports REST API act. Let's take a look at the next step here. You can run rest API requests to the instant AP pretty simply. We're just doing curl commands. So they're going to send a request with data in a JSON format and include that session identifier. Here's the curl command, master AP forward slash, and the API question mark with the SSID, the header content is JSON, and the data payload insecure, and so, a status message saying that that was successful. When you are ready to log out, you can issue a logout call, booting the session ID, and you should get a status zero saying that the user logout was successful. They make a note here that in the case of using double dash insecure, that's if you're using again a self-signed certificate, and you don't want to have any error messages there, you can just say, don't bother checking the signature on that certificate. That's going to be it. Let's do a quick demonstration of this on an Aruba Instant AP, and then we'll go ahead and wrap up. You can search for information on Aruba Instant REST API Guides based on your IP version. This will show documentation on how to login and logout. There are different types of previous APIs, like Action API, Configuration API, and a Monitoring API call. We can wrap up with a quick demonstration of how to access IP APIs set up in a Python script and that was put together. Opening my demo 6 folder, I have an IAP underscore requests py-file. Running the script logs into an AP, and shows the output for the command, show a PBS as a table. The result is one AP cluster member and one SSID that was configured; then the script logs out. If I review the script, you can see we are importing the request module. There is a defined login and logout function along with show commands. But these show commands are not sent to the SSH connection. Instead, they're using the Rest API. Show commands are going to be found in the monitoring API documentation, and the action API will allow adding new objects as well as making changes to the instant access points.
