Trouble adding Prisma Orchestrator to SolarWinds (ION CloudGenix monitoring)

I am trying to add Prisma Orchestrator (api.sase.paloaltonetworks.com) to SolarWinds but unable to login to the prisma orchestartor from the solarwinds web console. Has anyone else run into this?

I used this same credentials on this cURL command and was able to get an access token so not sure if that means the account is good or if there are other things to check on the Clougenix portal that I need to enable for this to work

curl -d "grant_type=client_credentials&scope=tsg_id:<id>" \
-u <service_account>:<password> \
-H "Content-Type: application/x-www-form-urlencoded" \
-X POST auth.apps.paloaltonetworks.com/.../access_token

0 mjheaberlin 9 months ago

I'm interested in this as well. I created a service account and when trying to add orchestrator in SolarWinds, the test fails.

emanc93 , based on the api.sase.paloaltonetworks.com URL, I'm assuming we need our SD-WAN devices migrated from the original CloudGenix portal over to Palo's portal. We're currently pending our migration to Strata Cloud Manager, still some things to iron out there. But I figured I would test adding the orchestrator in SolarWinds. Maybe I need to wait.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mjheaberlin 4 months ago in reply to mjheaberlin

Now that we are using Strata Cloud Manager (SCM), we've attempted this again and the SolarWinds software presents an error. "Login to Prisma Orchestrator failed: An error occurred while sending the request."

We have confirmed our client ID, client secret, and TSG ID are correct to retrieve an auth token and can successfully make API calls to the Unified SASE SD-WAN API (base URL: api.sase.paloaltonetworks.com) with it using Postman on the SolarWinds polling server.

We have a case open to troubleshoot further.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 exh200 19 days ago in reply to mjheaberlin

Any updates?
I am having the same issue, but we do not have support

login to Prisma Orchestrator failed: An error occurred while sending the request.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mjheaberlin 19 days ago in reply to exh200

Hi, so we did get this working. I know one issue was the @ symbol in the client ID, you need to change that to %40. I believe there may have also been issues with SW servers not trusting certs from the URLs (sorry I don't admin our SW, I'm on the Prisma SD-WAN side).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel