Skip to main content
You connect Aruba Central once at the MSP level. First check which platform your account is on: Central is managed from HPE GreenLake and has the new interface; Classic Central has its own API Gateway under Account Home. If your account shows the Classic Central toggle, connect Classic Central. Then find your cluster. Central shows its base URL under API Gateway > REST API (for example au1.api.central.arubanetworks.com is APAC-SOUTH1); Classic Central shows it under API Gateway > APIs (for example apigw-apacsouth.central.arubanetworks.com).

​
1a. Central: create a Personal API client

1

Open Personal API clients

Sign in to HPE GreenLake with your MSP workspace, and open Manage Workspace > Personal API clients.
2

Create the client

Click Create Personal API client and name it Neo. For an MSP workspace, choose HPE GreenLake Platform as the service, so Neo can act in each tenant. For a single account, you can choose your Central instance instead.
3

Copy the values

Copy the Client ID and Client Secret (GreenLake shows the secret only once). For a GreenLake Platform client, also copy the Workspace ID shown under Manage Workspace.
The client acts with your user’s role in Central. Give it a role that may do what your agents should do.

​
1b. Classic Central: create an app and token

1

Open the API Gateway

In Classic Central, open Account Home > Global Settings > API Gateway and the My Apps & Tokens tab (System Apps & Tokens as an admin).
2

Add the app

Click + Add Apps & Tokens, name the app Neo, choose Network Operations, and click Generate. Copy the app’s Client ID and Client Secret.
3

Download the token

In the Token List, click Download Token for the new token and copy its refresh_token.
Classic Central gives a new refresh token each time one is used, and Neo stores each new one. Enter the refresh token in Neo only, never in another tool, and do not revoke the token. If it stops working, Neo tells you in the dashboard inbox; generate a new token and save it again.

​
2. Add the client in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the HPE Aruba Networking Central card, under Networking.
2

Save the client

Pick the Platform and the Cluster, paste the Client ID and Client Secret, and add the Workspace ID (Central with a GreenLake Platform client) or the Refresh Token (Classic Central). Click Save. Neo checks them with Aruba before saving, so a wrong value is rejected straight away.
After the next PSA metadata sync, check the Organization Mapping tab: confirm each tenant’s company there.

​
3. Turn Aruba Central on per agent

Open the agent, go to its Tools & Settings tab, click Networking, and expand the HPE Aruba Networking Central block. Pick one of its Presets (Read Only, Helpdesk, IT Admin, Full Automation), or set each group yourself. See HPE Aruba Networking Central API for what each group covers.