diff --git a/pages/doc/csp_api_tokens.md b/pages/doc/csp_api_tokens.md index d5d181f41..bb55112c4 100644 --- a/pages/doc/csp_api_tokens.md +++ b/pages/doc/csp_api_tokens.md @@ -92,7 +92,7 @@ To generate and manage the API tokens for an existing **service account**: As a user with the **Admin** service role, you can view and revoke the API tokens of any service account in your service instance. -{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%} +{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%} 1. Log in to your service instance as an **Admin** user. 2. Click the gear icon on the toolbar and select **Accounts**. diff --git a/pages/doc/csp_invite-AoA-users_tutorial.md b/pages/doc/csp_invite-AoA-users_tutorial.md index 712280771..c1b37531c 100644 --- a/pages/doc/csp_invite-AoA-users_tutorial.md +++ b/pages/doc/csp_invite-AoA-users_tutorial.md @@ -61,7 +61,7 @@ We provide a number of built-in Tanzu Observability service roles. - A corresponding service role for each [permission](csp_permissions_overview.html#tanzu-observability-permissions). - Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service. -For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#otanzu-observability-service-roles-built-in). +For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#tanzu-observability-service-roles-built-in). ### Step 1: Enter the New User Details diff --git a/pages/doc/csp_migration.md b/pages/doc/csp_migration.md index 9c4da3aeb..21eef8c8a 100644 --- a/pages/doc/csp_migration.md +++ b/pages/doc/csp_migration.md @@ -266,7 +266,7 @@ For backward compatibility, all of your API tokens are **preserved** in Tanzu Ob * The Tanzu Observability API tokens associated with user accounts are **no longer** editable. The users can still use, view, and revoke their Tanzu Observability API tokens until they expire, but they **cannot** generate new ones. * The Tanzu Observability API tokens associated with service accounts are editable, because we still support them for a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens). -You should incrementally [replace](#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps. +You should incrementally [replace](#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token) your Tanzu Observability API tokens with VMware Cloud services API tokens and server to server OAuth apps. {% include tip.html content="From now on, all users must generate VMware Cloud services API tokens for their accounts and exchange them for access tokens. Users with the VMware Cloud **Organization Owner**, **Organization Administrator**, or **Organization Member** with **Developer** roles can create server to server OAuth apps and exchange the app credentials for access tokens."%} @@ -407,9 +407,9 @@ You should incrementally [replace](#how-to-replace-the-tanzu-observability-api-t During the process of onboarding your Tanzu Observability service to VMware Cloud services, all of the existing integrations are **preserved** and continue to operate using proxy authentication with Tanzu Observability API tokens. -You should incrementally [replace](#how-to-replace-the-csp_migration.html-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token. +You should incrementally [replace](#how-to-replace-the-tanzu-observability-api-token-of-a-wavefront-proxy) the proxy tokens of your [integrations](integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens) that are updated to use proxy authentication with the more secure VMware Cloud services access token. -{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-csp_migration.html-api-tokens) that still authenticate with Tanzu Observability API tokens."%} +{% include tip.html content="From now on, the users with the **Proxies** and **Integrations** service roles can set up integrations in your Tanzu Observability service. New integrations must use proxy authentication with VMware Cloud services access tokens except for the [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens) that still authenticate with Tanzu Observability API tokens."%}