Skip to content

Commit df8cd96

Browse files
helenjwhelenjw
authored
Revert "Add documentation for new organization level user-token-enabled setti…" (#951)
This reverts commit 5b103c1.
1 parent 5b103c1 commit df8cd96

File tree

3 files changed

+5
-36
lines changed

3 files changed

+5
-36
lines changed

‎content/terraform-docs-common/docs/cloud-docs/api-docs/organizations.mdx‎

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -134,8 +134,7 @@ curl \
134134
"owners-team-saml-role-id": null,
135135
"two-factor-conformant": false,
136136
"assessments-enforced": false,
137-
"default-execution-mode": "remote",
138-
"user-tokens-enabled": true
137+
"default-execution-mode": "remote"
139138
},
140139
"relationships": {
141140
"default-agent-pool": {
@@ -224,8 +223,7 @@ curl \
224223
"owners-team-saml-role-id": null,
225224
"two-factor-conformant": false,
226225
"assessments-enforced": false,
227-
"default-execution-mode": "remote",
228-
"user-tokens-enabled": true
226+
"default-execution-mode": "remote"
229227
},
230228
"relationships": {
231229
"default-agent-pool": {
@@ -360,8 +358,7 @@ curl \
360358
"owners-team-saml-role-id": null,
361359
"two-factor-conformant": false,
362360
"assessments-enforced": false,
363-
"default-execution-mode": "remote",
364-
"user-tokens-enabled": true
361+
"default-execution-mode": "remote"
365362
},
366363
"relationships": {
367364
"default-agent-pool": {
@@ -433,7 +430,6 @@ Properties without a default value are required.
433430
| `data.attributes.default-execution-mode` | string | `remote` | Which [execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode) to use by default. Valid values are `remote`, `local`, and `agent`. |
434431
| `data.attributes.default-agent-pool-id` | string | (previous value) | Required when `default-execution-mode` is set to `agent`. The ID of the agent pool belonging to the organization. Do _not_ specify this value if you set `execution-mode` to `remote` or `local`. |
435432
| `data.attributes.enforce-hyok` | boolean | false | Whether or not new workspaces within the organization are created with hold your own key enabled. Your organization must have a primary HYOK configuration before enabling `enforce-hyok`. Hold your own key is only available in HCP Terraform, [learn more](/terraform/cloud-docs/hold-your-own-key). |
436-
| `data.attributes.user-tokens-enabled` | boolean | true | Whether or not user tokens can access an organization's resources through the API. Defaults to `true`. |
437433

438434
### Sample Payload
439435

@@ -516,8 +512,7 @@ curl \
516512
"owners-team-saml-role-id": null,
517513
"two-factor-conformant": false,
518514
"assessments-enforced": false,
519-
"default-execution-mode": "remote",
520-
"user-tokens-enabled": true
515+
"default-execution-mode": "remote"
521516
},
522517
"relationships": {
523518
"default-agent-pool": {
@@ -627,7 +622,6 @@ This PATCH endpoint requires a JSON object with the following properties as a re
627622
| `data.attributes.default-execution-mode` | string | `remote` | Which [execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode) to use by default. Valid values are `remote`, `local`, and `agent`. |
628623
| `data.attributes.default-agent-pool-id` | string | (previous value) | Required when `default-execution-mode` is set to `agent`. The ID of the agent pool belonging to the organization. Do _not_ specify this value if you set `execution-mode` to `remote` or `local`. |
629624
| `data.attributes.enforce-hyok` | boolean | false | Whether or not new workspaces within the organization are created with hold your own key (HYOK) enabled. Your organization must have a primary HYOK configuration before enabling `enforce-hyok`. Hold your own key is only available in HCP Terraform, [learn more](/terraform/cloud-docs/hold-your-own-key). |
630-
| `data.attributes.user-tokens-enabled` | boolean | true | Whether or not user tokens can access an organization's resources through the API. Defaults to `true`. |
631625

632626
### Sample Payload
633627

@@ -708,8 +702,7 @@ curl \
708702
"owners-team-saml-role-id": null,
709703
"two-factor-conformant": false,
710704
"assessments-enforced": false,
711-
"default-execution-mode": "remote",
712-
"user-tokens-enabled": true
705+
"default-execution-mode": "remote"
713706
},
714707
"relationships": {
715708
"default-agent-pool": {

‎content/terraform-docs-common/docs/cloud-docs/users-teams-organizations/api-tokens.mdx‎

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -16,26 +16,6 @@ Refer to [Team Token API](/terraform/cloud-docs/api-docs/team-tokens) and [Organ
1616

1717
API tokens may belong directly to a user. User tokens are the most flexible token type because they inherit permissions from the user they are associated with. For more information on user tokens and how to generate them, see the [Users](/terraform/cloud-docs/users-teams-organizations/users#tokens) documentation.
1818

19-
### Disable user tokens for organizations
20-
21-
By default, user tokens are enabled for organizations. When your organization disables user tokens, the HCP Terraform API blocks user tokens from accessing organization resources.
22-
23-
To disable user tokens for your organization, perform the following steps:
24-
1. Sign in to [HCP Terraform](https://app.terraform.io/) or Terraform Enterprise, then navigate to the organization where you want to disable user tokens.
25-
1. Choose **Settings** from the sidebar, then **API tokens**.
26-
1. From the **User Tokens** tab, uncheck the **Allow members to access organization resources with their user tokens** setting.
27-
1. Click **Update settings**.
28-
1. In the confirmation modal, select **Disable**.
29-
1. User tokens are now disabled for this organization.
30-
31-
If your organization has automations that authenticate using user tokens, disabling user tokens can cause those automations to fail.
32-
33-
<Note>
34-
35-
An organization that disables user tokens cannot connect to VCS using the [Github (App)](/terraform/cloud-docs/vcs/github-app), because it relies on user tokens to authenticate. Your organization can use [Github (OAuth) to configure their VCS connections](/terraform/cloud-docs/vcs/github) instead.
36-
37-
</Note>
38-
3919
## Team API Tokens
4020

4121
API tokens may belong to a specific team. Team API tokens allow access to the workspaces that the team has access to, without being tied to any specific user.

‎content/terraform-docs-common/docs/cloud-docs/users-teams-organizations/users.mdx‎

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -191,10 +191,6 @@ To revoke a token, click the **trash can** next to it. That token will no longer
191191

192192
~> **Note**: HCP Terraform does not revoke a user API token's access to an organization when you remove the user from an SSO Identity Provider as the user may still be a member of the organization. To remove access to a user's API token, remove the user from the organization in the UI or with the [Terraform Enterprise provider](https://registry.terraform.io/providers/hashicorp/tfe/latest).
193193

194-
#### Tokens disabled
195-
196-
User tokens can be disabled at the organization level, for more information refer to [User API tokens](/terraform/cloud-docs/users-teams-organizations/api-tokens#user-api-tokens).
197-
198194
### GitHub app OAuth token
199195

200196
Click **Tokens** in the sidebar to manage your GitHub App token. This token lets you connect a workspaces to an available GitHub App installation.

0 commit comments

Comments
 (0)