Overview
To enhance device intelligence, you can integrate Aruba device data with Cato’s device discovery for the IoT/OT Security service. Data from both platforms is merged, creating unified device profiles that enhance visibility and classification.
The combined view appears on the Home > Devices > Inventory tab and helps improve identification of both managed and unmanaged assets. With more accurate and complete device data, you can make better-informed security decisions across your network. For more information on Device Inventory, see What is Device Inventory?.
To configure the Device Management integration, you need to:
Configure the integration in Aruba Networks
Create the API connector in the CMA
An IoT/OT Security license is required for this feature.
Configuring the Aruba Networks Integration
To configure the Aruba Networks integration, create API credentials for Central or Classic Central and enter them in the Cato Management Application (CMA).
Prerequisites
An HPE Aruba Networking Central or Classic Central account with access to the sites you want to monitor
For Central: permission to create a Personal API client in HPE GreenLake for your Central instance
For Classic Central: permission to create an application and token in the Classic Central API Gateway
For Central only: devices assigned to a site, because Central's monitoring APIs only report telemetry for site-assigned devices
The access token inherits the same rights and permissions as your Central user role. Use an account whose role has read access to the monitoring data you want to collect.
Step 1: Configure the Integration in Aruba Networks
The connector supports both Central (New Central) and Classic Central. Create one Aruba Networks connector per Central account.
Central: Use this option for standalone Central accounts or access points running AOS 10
Classic Central: Use this option if you see the Classic Central toggle or have AOS 8 Instant APs managed in Classic Central
To configure Aruba Central:
Log in to your HPE Aruba Networking Central account.
Navigate to Menu > API Gateway, and select the REST API tab.
Click Copy next to the Base URL. Copy and save the Base URL so it can be entered into the CMA.
The Base URL is specific to your account's hosting region. Requests are unsuccessful if you use the wrong URL.
In HPE GreenLake, select Manage Workspace.
Select the Personal API clients category and click Create Personal API client.
Enter a credential nickname, such as
Cato Network Infrastructure, and choose your Central instance from the service manager dropdown.Click Create personal API client.
Copy and save the Client ID and Client Secret so they can be entered into the CMA.
Confirm that the access points you want to monitor are assigned to a site. Unassigned devices return no monitoring data and do not appear in Cato.
To configure Aruba Classic Central:
Identify the Classic API Gateway URL for your account's cluster. Classic Central uses different API Gateway domains from Central.
US-1:
https://app1-apigw.central.arubanetworks.comUS-2:
https://apigw-prod2.central.arubanetworks.comUS-East1:
https://apigw-us-east-1.central.arubanetworks.comUS-West4:
https://apigw-uswest4.central.arubanetworks.comUS-West5:
https://apigw-uswest5.central.arubanetworks.comEU-1:
https://eu-apigw.central.arubanetworks.comEU-Central2:
https://apigw-eucentral2.central.arubanetworks.comEU-Central3:
https://apigw-eucentral3.central.arubanetworks.comCanada-1:
https://apigw-ca.central.arubanetworks.comChina-1:
https://apigw.central.arubanetworks.com.cnAPAC-1:
https://api-ap.central.arubanetworks.comAPAC-EAST1:
https://apigw-apaceast.central.arubanetworks.comAPAC-SOUTH1:
https://apigw-apacsouth.central.arubanetworks.comUAE-NORTH1:
https://apigw-uaenorth1.central.arubanetworks.com
Copy and save the Classic API Gateway URL so it can be entered into the CMA.
Log in to Classic Central. On the Account Home page, under Global Settings, click API Gateway.
Open the My Apps & Tokens tab. (Admin users can instead use the System Apps & Tokens tab.)
Click + Add Apps & Tokens.
Enter an application name, such as
Cato Network Infrastructure. Leave Redirect URI empty and select Network Operations as the application.Click Generate. The application is added to the table, and a token is added to the Token List.
From the application's row, copy and save the Client ID and Client Secret so they can be entered into the CMA.
In the Token List, click Download Token for the new token. Copy and save the Refresh Token (
refresh_token) so it can be entered into the CMA.Complete the Cato connection within 15 minutes of generating the token. Use this application and token only for Cato. Classic Central issues a new token pair when the token is refreshed. If another tool or script refreshes the same token, Cato's copy stops working.
Build the Token Endpoint by appending
/oauth2/tokento the Classic API Gateway URL. For US-2, usehttps://apigw-prod2.central.arubanetworks.com/oauth2/token.
Step 2: Create the API Connector in the CMA
After you have set up an integration with the required application, add the details in the CMA.
For Aruba Networks, use the authentication option that matches your account:
OAuth2 Client Credentials authorization for Aruba Central: Client ID, Client Secret, and Aruba Central API Gateway URL
OAuth2 refresh token authentication for Aruba Classic Central: Client ID, Client Secret, Refresh Token, Token Endpoint, and Aruba Classic Central API Gateway URL
To create the API connector in the CMA:
From the navigation menu, click Resources > Integrations.
Click the Configured Integrations tab.
Click New. The New Integration panel opens.
Select the SaaS Application you want to add.
In the Capability drop-down, select Device Management.
Add the details created during step one.
Click Save.
The app is visible on the Integrated Apps table with a Connected status.
With Central, Cato automatically discovers all sites in your account and begins collecting events from each site. With Classic Central, Cato collects events, access points, and wireless clients across the account and renews the token automatically.
If the connection shows Aruba Classic Central refresh token invalid, the token has expired, was revoked, or was refreshed by another tool. Generate a new token for the application in API Gateway > My Apps & Tokens. Copy and save the Refresh Token so it can be entered into the CMA. Edit the connector in Cato and paste the new Refresh Token.
Known Limitations
Wired clients are not collected with Classic Central. The Classic Central option collects wireless clients only.
Usernames are only available on 802.1X networks. Aruba populates a client username only when the SSID uses 802.1X / WPA-Enterprise against a RADIUS backend. On pre-shared-key SSIDs: typically guest, IoT, and BYOD networks: there is no per-user identity to report, so client events from those networks have no user attribution.
With Central, only site-assigned devices are reported. Devices not assigned to a site in Central are not visible to the Central APIs. If your devices are managed in Classic Central, use the Classic Central authentication option instead.
The Classic Central token must be dedicated to Cato. If another tool refreshes the same token, or the token is not used for 15 days, the connection stops and you need to generate a new token.
API quotas. Central enforces a shared rate limit of 10 API calls per second across the whole Central account. Classic Central enforces 7 API calls per second and a daily API call quota per account: 5,000 calls a day as a base, rising with the number of subscribed devices at 30 calls per Foundation device and 90 calls per Advanced device per day once that total exceeds 5,000. The Classic Central connector uses about 400 calls a day (at least four per poll: token refresh, access points, clients, and events), more on large accounts because each list is read in pages of 1,000. Other tools sharing the account count against the same quota.