Hi,
I think, it will be better to open an issue on TAC
------------------------------
PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...
PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)
PowerArubaCL: Powershell Module to use Aruba Central
PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..
ACEP / ACMX #107 / ACDX #1281
------------------------------
Original Message:
Sent: Oct 09, 2025 04:58 PM
From: Allen Unrau
Subject: Issue with ca1 endpoint
Hello everyone
I may have discovered an issue with the ca1 endpoint at ca1.api.central.arubanetworks.com. This is what I'm seeing:
I generate personal API client and access token via Greenlake web UI - this works ok. My workspace is in Canada.
Using New Central api gateway at https://developer.arubanetworks.com/new-central/reference/
Use generated token on de1.api.central… -> yields a response 401, Invalid access token (this is expected)
Use token on us1.api.central… -> yields a response 401, Invalid access token (this is expected)
Use token on ca1.api.central…-> no response code, the "Try It!" button turns into a spinner and never changes back. When I check the Javascript console, I see a CORS policy error:
I also tried this:
Use a junk token on de1.api.central… - yields a response 401, Invalid access token (this is expected)
Use a junk token on ca1.api.central… - no response code, the "Try It!" button turns into a spinner and never changes back. Same CORS error in Javascript console as above.
I think this indicates an issue with the ca1 endpoint. Is anyone using that one?
-------------------------------------------