06-21-2023 05:09 PM
Generating an access-token for the Automated Software Distribution API results in an "invalid client" error message. I've tried regenerating the API keys several times with the same error message. I've been using postman to test and verified that the request matches the documentation exactly. The HTTP request is below. Am I missing something obvious?
POST /as/token.oauth2 HTTP/1.1
Host: cloudsso.cisco.com
Content-Type: application/x-www-form-urlencoded
Cookie: PF=i7uSj3x5GzpZAqXI451Ksf
Content-Length: 103
grant_type=client_credentials&client_id=xxxxxxxxxxxxxxx&client_secret=zzzzzzzzzzzzzzzzzzz
06-23-2023 08:51 AM
Dear Team,
I have the same issue in other API calls.
Even though I am authenticated and have the correct token, it seems that my application is not able to use the new apx.cisco.com environment.
it seems that we don't have access to https://anypoint.mulesoft.com/apiplatform/apx/#/portals
07-31-2023 08:03 AM
For anyone having this issue, Cisco's documentation is wrong and the correct application URL is "https://id.cisco.com/oauth2/default/v1/token", not cloudsso.cisco.com. Additionally, all requests should be sent to https://apix.cisco.com/software and not the "https://api.cisco.com/software" URL referenced in their documentation.
08-08-2023 04:00 AM - edited 08-09-2023 12:09 AM
-
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide