Loading...
Loading...
If we create/register a new application on https://apiconsole.cisco.com after March 1 2023, we will not be able to enable SD-AVC Cloud Connector, process will fail with error: "CREDENTIALS". It has been a change on the API calls url recently according to this document. https://apiconsole.cisco.com/docs/read/overview/Migrating_Applications Application registered before March 1,2023 will be using URL https://cloudsso.cisco.com/as/token.oauth2 (being deprecated). For Application created beginning March 1, 2023 you will use https://id.cisco.com/oauth2/default/v1/token. vManage SD-AVC container still is making API calls on url cloudsso.cisco.com and this is causing the process to fail 023-03-08 19:01:23 INFO CloudGatwayApi:47 - AWS API is triggered 2023-03-08 19:01:23 INFO CloudAmazonApi:470 - connectivity-check url: 2023-03-08 19:01:23 INFO CloudAmazonApi:485 - connectivity-check. try 0 2023-03-08 19:01:23 INFO CloudAmazonApi:490 - connectivity-check took in Msec:20 2023-03-08 19:01:23 INFO CloudGatwayApi:47 - AWS API is triggered 2023-03-08 19:01:23 INFO CloudAmazonApi:265 - generate token. is sdwan credentials=false 2023-03-08 19:01:23 WARN CloudAmazonApi:287 - generate token failed org.springframework.web.client.HttpClientErrorException$Unauthorized: 401 Unauthorized: [no body] We can see on the packet capture too that API is going on cloudsso.cisco.com 372 2023-03-08 19:21:15.423162 XX.XX.XX.XX 38348 YY.YY.YY.YYY 53 DNS 78 Standard query 0x5c24 A cloudsso.cisco.com Default
1. vManage is using SDAVC Cloud Connector. 2. The API key for Cloud Connector is generated after March 1, 2023.
At this time there is no workaround. Please open a TAC case.
N/A
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.