HTTP/s 401 error generated when configuring the Aruba Central plugin

Products

• Network Observability
• Virtual Network Assurance

Issue/Introduction

When configuring the Aruba Central plugin, alarms and/or inventory is not shown in Spectrum with the following errors seen in the VNA oc.log:

2025-12-16 04:50:01,189 ERROR (EE-ManagedThreadFactory-default-Thread-7) Aruba_xxx-xxxx-xxxx-xxxx=Notification Poll [OC_ACQUISITION] TimHttpFunction 337  Error while sending http request to https://xxxx.aruba.com/monitoring/v2/events?device_type=SWITCH&event_type=FFI&from_timestamp=1765813200&to_timestamp=1765813800&calculate_total=true&limit=1000&offset=0 :
...
java.io.IOException: Server returned HTTP response code: 401 for URL: https://xxxx.aruba.com/monitoring/v2/events?device_type=SWITCH&event_type=FFI&from_timestamp=1765813200&to_timestamp=1765813800&calculate_total=true&limit=1000&offset=0

and/or

2025-12-16 09:00:05,147 ERROR (EE-ManagedThreadFactory-default-Thread-4) Aruba_xxx-xxxx-xxxx-xxxxx=Inventory Poll [OC_ACQUISITION] TimHttpFunction 337  Error while sending http request to https://xxxx.aruba.com/central/v2/sites?calculate_total=true&limit=1000&offset=0 :
...
java.io.IOException: Server returned HTTP response code: 401 for URL: https://xxxx.aruba.com/central/v2/sites?calculate_total=true&limit=1000&offset=0

Environment

DX Netops VNA all supported versions

Cause

All the tokens must be correct. These are detailed in:

TechDocs : DX NetOps VNA 25.4 : Plugins - Aruba Central

These tokens are:

    "ARUBA_CLIENT_ID": "xxxxxx"
    "ARUBA_CLIENT_SECRET": "xxxxxx",
    "ARUBA_ACCESS_TOKEN": "xxxxxx",
    "ARUBA_REFRESH_TOKEN" : "xxxxxx",

Resolution

Make sure all the tokens are correct and the access/refresh tokens have not expired.

Additional Information

NOTE: the access token expires within 2 hours, the refresh token expires in 14 days.

Curl can be used to verify the refresh token as follows:

curl --location --request POST 'https://<aruba-url>/oauth2/token?client_id=<ARUBA_CLIENT_ID>&grant_type=refresh_token&client_secret=<ARUBA_CLIENT_SECRET>&refresh_token=<ARUBA_REFRESH_TOKEN>' --header 'Content-Type: application/json'

If you need to use a proxy add;

--proxy '<http|https>://username:password@proxynameorip:proxyport' 

Use the apropriate protocol and other details