PaloAltoNetworks / PaloAltoNetworks/pan.dev

Issue/Help with "Get OAuth Token"

Open Beginner friendly
#1,304 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
MDX
Stars
78
Forks
88
Avg merge
5d 17h
Merged PRs (30d)
18

Description

Documentation link

Describe the problem

Prisma AIRS OAuth Token endpoint doc issue**
While working with the Management API endpoint POST /v1/mgmt/oauth/client_credential/accesstoken (https://pan.dev/prisma-airs/api/airuntimesecurity/management/get-apigee-oauth-token/)), I found that the client_id field in the request body is misleading.
What the doc says:
The body expects client_id (string) — which implies the OAuth Client ID from your service account.
What actually works:
The client_id field must be your API key (the x-pan-token value), not the OAuth Client ID.
So the working curl looks like this:

curl -L 'https://api.sase.paloaltonetworks.com/aisec/v1/mgmt/oauth/client_credential/accesstoken' \
  -H 'Authorization: Bearer <SASE_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "<YOUR_X_PAN_TOKEN>",
    "customer_app": "<YOUR_APP_NAME>"
  }'

Using the actual OAuth Client ID returns "GetApigeeOauthToken: API key not found".

Suggested fix

What actually works:
The client_id field must be your API key (the x-pan-token value), not the OAuth Client ID.
So the working curl looks like this:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Prisma AIRS documentation page for POST /v1/mgmt/oauth/client_credential/accesstoken linked in the issue. Verify the request-body description and curl example against the reported behavior, then update the client_id guidance so the documentation matches the working x-pan-token value; done when the example and field description are consistent.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.