This article with help you to set up PULT Wifi with Aruba Cloud.
Prerequisites
- Need (read-only) API-Access to Aruba Central
You can either do the Steps with any Aruba Central account that has enough permissions to view the “Clients” or you can create a new separate “service account” that has reduced (preferably read-only) permissions to view the “Clients” and is able to create API Tokens.
However, please note that we also need the username and password for that service account.
You can find further instructions on creating a service account in the appendix (at the bottom).
Steps:
-
Go to your Aruba Central dashboard, login with your service account and navigate to
Global View > Maintain > Organization > Platform Integration
and click on REST API. -
Go to the
System Apps and Tokens
tab and click onAdd Apps & Token
. A modal will popup, then click onGenerate
. -
Note down the
Client ID
andClient Secret
. -
Go back to the
APIs
tab and note down the API URL. -
Finally, note down the Aruba Central Customer ID.
Conclusion
At the end you will have the following data that you need to share with us:
- Kandji
- API URL
- API Token
- Aruba Central
- API URL (From step 4)
- Aruba Central Customer ID (From step 5)
- App Client Id & Secret (From step 3)
- Username & Passwod for the service account (See appendix)
Appendix
Creating a service account
A service account is simply a user with limited read-only permissions, which Pult can use to view resources in your Aruba Central. The service account's credentials consist of a username and password that must be shared with Pult for the system to function properly.
There might be many ways to create such an account. Down below is one possible way to approach this.
Prerequisites
Most of the operations down below require higher privileges.
Steps
-
Login to HP GreenLake (ideally with an admin account that has permissions to create user and assign roles). Then navigate to the Users page (https://common.cloud.hpe.com/manage-account/identity/users) and click on
Invite User
. Enter an available email address for the service account and set the GreenLake role to an appropriate role (ideally with limited read-only permissions, e.g.Workspace Observer
). -
After the user has been activated (through the invite). Assign the required role
Aruba Central View Only
for the service managerAruba Central
.Note: You can also add resource restrictions to limit Pult's access to specific networks you designate (still read-only).
-
Done. Please note down the username and password.