PaloAltoNetworks / PaloAltoNetworks/pan.dev
Issue/Help with "Create an access token"
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 78
- Forks
- 88
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 18
Description
Documentation link
https://pan.dev/scm/api/auth/post-auth-v-1-oauth-2-access-token/
Describe the problem
Customers in general do not like Basic Auth and are starting to block it by stripping out the header "Authorization: Basic" from proxies.
Suggested fix
We should change the documentation to put the client id and client secret in the body. Yes, this works already.
curl -s -X POST https://auth.apps.paloaltonetworks.com/oauth2/access_token
-H "Content-Type: application/x-www-form-urlencoded"
-d "grant_type=client_credentials&scope=tsg_id:<tsg_id>&client_id=<client_id>&client_secret=<client_secret>"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked “Create an access token” documentation page and review its current authentication example. Update the documentation to show client_id and client_secret in the request body, using the supplied form-encoded example; done means the page clearly documents this working alternative to Basic Auth.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100