You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/tutorials/secure-your-organization/respond-to-a-security-incident.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,16 +101,18 @@ There are several containment actions you can choose to perform to limit the att
101
101
102
102
For exposed or exploited credentials, the most immediate action you can take is to revoke the affected credentials to prevent further misuse.
103
103
104
-
{% ifversion fpt or ghec or ghes > 3.17 %}
104
+
{% ifversion fpt or ghec %}
105
+
105
106
***Revoke via the API**
106
107
107
108
If the token is one of the following types, and the literal value of the token is known, you (or anybody) can revoke it by **submitting a request via the REST API**. See [AUTOTITLE](/rest/credentials/revoke?apiVersion=2022-11-28#revoke-a-list-of-credentials).
108
109
109
110
* {% data variables.product.pat_v1_caps %}
110
-
* {% data variables.product.pat_v2_caps %}{% ifversion fpt or ghec or ghes > 3.20 %}
111
+
* {% data variables.product.pat_v2_caps %}
111
112
* {% data variables.product.prodname_oauth_app %} access token
112
113
* {% data variables.product.prodname_github_app %} user access token
113
-
* {% data variables.product.prodname_github_app %} refresh token{% endif %}
114
+
* {% data variables.product.prodname_github_app %} refresh token
Copy file name to clipboardExpand all lines: content/organizations/managing-programmatic-access-to-your-organization/github-credential-types.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ The following sections describe revocation options for each credential type base
38
38
39
39
* If the token **belongs to you**, you can delete it via your personal account settings. See [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#deleting-a-personal-access-token).
40
40
{% data reusables.credentials.revoke-via-api %}
41
-
***Organization owners** and **enterprise owners** do not have direct visibility into or control over individual tokens. However, they can:{% ifversion fpt or ghec or ghes > 3.17 %}
41
+
***Organization owners** and **enterprise owners** do not have direct visibility into or control over individual tokens. However, they can:{% ifversion fpt or ghec %}
42
42
* Revoke them using the REST API, if the actual token value is known. See [AUTOTITLE](/rest/credentials/revoke?apiVersion=2022-11-28#revoke-a-list-of-credentials).{% endif %}
43
43
* Restrict the access of {% data variables.product.pat_generic_plural %} to the organization or enterprise entirely. See [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization) and [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise).
44
44
***Organization owners and enterprise owners** on {% data variables.product.prodname_ghe_cloud %} with SSO enforced can revoke the SSO authorization for a specific {% data variables.product.pat_v1 %}. See [Revoking SSO authorization](#revoking-sso-authorization) for details.
@@ -49,7 +49,7 @@ The following sections describe revocation options for each credential type base
49
49
* If the token **belongs to you**, you can delete it via your personal account settings. See [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#deleting-a-personal-access-token).
50
50
{% data reusables.credentials.revoke-via-api %}
51
51
***Organization owners**: Can view and revoke individual tokens. Note, however, that when an organization owner revokes a {% data variables.product.pat_v2 %}, any SSH keys created by the token will continue to work and the token will still be able to read public resources within the organization. The revocation changes the resource owner from the organization to the user, and the user can reassign it back. See [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization).
52
-
***Organization owners** and **enterprise owners** can:{% ifversion fpt or ghec or ghes > 3.17 %}
52
+
***Organization owners** and **enterprise owners** can:{% ifversion fpt or ghec %}
53
53
* Revoke the token using the REST API. See [AUTOTITLE](/rest/credentials/revoke?apiVersion=2022-11-28#revoke-a-list-of-credentials).{% endif %}
54
54
* Restrict the access of {% data variables.product.pat_generic_plural %} to the organization or enterprise entirely. See [AUTOTITLE](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization) and [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise).
55
55
***Revoked automatically** if pushed to a public repository or gist, or if unused for one year. See [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation).
* If the token is owned by someone else, and the actual token value is known, **anyone** can submit a request to revoke it using the REST API. The API doesn't require authentication - anyone with the token value can submit it for revocation. See [AUTOTITLE](/rest/credentials/revoke?apiVersion=2022-11-28#revoke-a-list-of-credentials) in the REST API documentation.{% endif %}
Copy file name to clipboardExpand all lines: src/rest/data/fpt-2022-11-28/billing.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@
28
28
},
29
29
{
30
30
"name": "per_page",
31
-
"description": "<p>The number of results per page (max 10).</p>",
31
+
"description": "<p>The number of results per page (max 100).</p>",
32
32
"in": "query",
33
33
"schema": {
34
34
"type": "integer",
@@ -61,7 +61,7 @@
61
61
}
62
62
],
63
63
"bodyParameters": [],
64
-
"descriptionHTML": "<p>Gets all budgets for an organization. The authenticated user must be an organization admin or billing manager.\nEach page returns up to 10 budgets.</p>",
64
+
"descriptionHTML": "<p>Gets all budgets for an organization. The authenticated user must be an organization admin or billing manager.\nEach page returns up to 100 budgets.</p>",
Copy file name to clipboardExpand all lines: src/rest/data/fpt-2026-03-10/billing.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@
28
28
},
29
29
{
30
30
"name": "per_page",
31
-
"description": "<p>The number of results per page (max 10).</p>",
31
+
"description": "<p>The number of results per page (max 100).</p>",
32
32
"in": "query",
33
33
"schema": {
34
34
"type": "integer",
@@ -61,7 +61,7 @@
61
61
}
62
62
],
63
63
"bodyParameters": [],
64
-
"descriptionHTML": "<p>Gets all budgets for an organization. The authenticated user must be an organization admin or billing manager.\nEach page returns up to 10 budgets.</p>",
64
+
"descriptionHTML": "<p>Gets all budgets for an organization. The authenticated user must be an organization admin or billing manager.\nEach page returns up to 100 budgets.</p>",
0 commit comments