From e4d703fd6d639626b1e0a8f5a199894c97ae306d Mon Sep 17 00:00:00 2001 From: Abinaya Kubendhiran Date: Wed, 8 Jul 2026 14:35:47 +0530 Subject: [PATCH 1/3] Modified the curl as per the old link https://pan.dev/sase/api/auth/post-auth-v-1-oauth-2-access-token/ --- products/scm/docs/access-tokens.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/products/scm/docs/access-tokens.md b/products/scm/docs/access-tokens.md index edd14b84d..dc64fc440 100644 --- a/products/scm/docs/access-tokens.md +++ b/products/scm/docs/access-tokens.md @@ -31,10 +31,11 @@ to create an access token. Be aware that: For example: - curl -d "grant_type=client_credentials&scope=tsg_id:" \ - -u : \ - -H "Content-Type: application/x-www-form-urlencoded" \ - -X POST https://auth.apps.paloaltonetworks.com/oauth2/access_token + curl -L -X POST 'https://auth.apps.paloaltonetworks.com/auth/v1/oauth2/access_token' \ + -H 'Content-Type: application/x-www-form-urlencoded' \ + -H 'Accept: application/json' \ + -H 'Authorization: Basic PHVzZXJuYW1lPjo8cGFzc3dvcmQ+' \ + -d '' **Note**: The service account that you use to authenticate this request must belong to the TSG that you identify on the `scope` field. See [Acess Token Scopes](/scm/docs/scope) for more information. From 924b3181d0ffd47c0e1d622a07af13925c15c8a5 Mon Sep 17 00:00:00 2001 From: Abinaya Kubendhiran Date: Wed, 8 Jul 2026 16:34:23 +0530 Subject: [PATCH 2/3] made edits to test pushing the branch to remote from vs code --- products/scm/docs/access-tokens.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/products/scm/docs/access-tokens.md b/products/scm/docs/access-tokens.md index dc64fc440..9837f44bd 100644 --- a/products/scm/docs/access-tokens.md +++ b/products/scm/docs/access-tokens.md @@ -14,8 +14,8 @@ and [created a service account](/scm/docs/service-accounts) that has role-access When you did these things, you obtained: - A TSG ID, which you use to identify the scope of the access token. -- A Client ID -- A Client Secret +- A Client ID +- A Client Secret Using this information, you can use [POST /oauth2/access_token](/scm/api/auth/post-auth-v-1-oauth-2-access-token) @@ -47,7 +47,7 @@ Access tokens have a lifespan of 15 minutes. If your access token is incorrect, the API request may not go through, and the resulting error indicates an invalid authorization code. -You can check your access token's credentials by pasting the access token into https://jwt.io/ . +You can check your access token's credentials by pasting the access token into https://jwt.io/. This decodes the token to determine whether the actual set of credentials matches the set of credentials present in the access token. From fb2e69463c33753aa5276093e2cd9d5400e32b2a Mon Sep 17 00:00:00 2001 From: Abinaya Kubendhiran Date: Fri, 10 Jul 2026 11:42:42 +0530 Subject: [PATCH 3/3] modified the sample curl command based on the comment from Jonathan Ames, SME. --- products/scm/docs/access-tokens.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/products/scm/docs/access-tokens.md b/products/scm/docs/access-tokens.md index 9837f44bd..15ec6798c 100644 --- a/products/scm/docs/access-tokens.md +++ b/products/scm/docs/access-tokens.md @@ -31,11 +31,12 @@ to create an access token. Be aware that: For example: - curl -L -X POST 'https://auth.apps.paloaltonetworks.com/auth/v1/oauth2/access_token' \ - -H 'Content-Type: application/x-www-form-urlencoded' \ - -H 'Accept: application/json' \ - -H 'Authorization: Basic PHVzZXJuYW1lPjo8cGFzc3dvcmQ+' \ - -d '' + curl --location 'https://auth.apps.paloaltonetworks.com/auth/v1/oauth2/access_token' \ + --header 'Content-Type: application/x-www-form-urlencoded' \ + --data-urlencode 'grant_type=client_credentials' \ + --data-urlencode 'scope=tsg_id:' \ + --data-urlencode 'client_id=' \ + --data-urlencode 'client_secret=' **Note**: The service account that you use to authenticate this request must belong to the TSG that you identify on the `scope` field. See [Acess Token Scopes](/scm/docs/scope) for more information.