Update links for Tanzu 11 and the latest tile/broker versions

docs/docs/v4/connectors/microsoft-sql-server.md

@@ -146,8 +146,8 @@ A complete sample app that uses Entity Framework Core with SQL Server is provide
 
 This Connector supports the following service brokers:
 
-- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-13/csb-azure/reference-azure-mssql-db.html)
-- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-mssql.html)
+- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-15/csb-azure/reference-azure-mssql-db.html)
+- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-17/csb-aws/reference-aws-mssql.html)
 
 You can create and bind an instance to your application by using the Cloud Foundry CLI.
 

docs/docs/v4/connectors/mongodb.md

@@ -104,7 +104,7 @@ A complete sample app that uses `IMongoClient` is provided at https://github.com
 
 This Connector supports the following service brokers:
 
-- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-13/csb-azure/reference-azure-cosmosdb-mongo.html)
+- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-15/csb-azure/reference-azure-cosmosdb-mongo.html)
 
 You can create and bind an instance to your application by using the Cloud Foundry CLI.
 

docs/docs/v4/connectors/mysql.md

@@ -153,9 +153,9 @@ A complete sample app that uses Entity Framework Core with MySQL is provided at
 
 This Connector supports the following service brokers:
 
-- [Tanzu for MySQL on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/11-0/mysql-tp/index.html)
-- [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-8/csb-gcp/reference-gcp-mysql.html)
-- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-mysql.html)
+- [Tanzu for MySQL on Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-mysql-tanzu-platform/11-0/mysql-tp/index.html)
+- [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-10/csb-gcp/reference-gcp-mysql.html)
+- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-17/csb-aws/reference-aws-mysql.html)
 
 You can create and bind an instance to your application by using the Cloud Foundry CLI.
 

docs/docs/v4/connectors/postgresql.md

@@ -147,9 +147,9 @@ A complete sample app that uses Entity Framework Core with PostgreSQL is provide
 
 This Connector supports the following service brokers:
 
-- [Tanzu for Postgres on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-postgres-tanzu-platform/11-0/postgres-tp/index.html)
-- [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-8/csb-gcp/reference-gcp-postgresql.html)
-- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-postgres.html)
+- [Tanzu for Postgres on Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-postgres-tanzu-platform/11-0/postgres-tp/index.html)
+- [Tanzu Cloud Service Broker for GCP](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-gcp/1-10/csb-gcp/reference-gcp-postgresql.html)
+- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-17/csb-aws/reference-aws-postgres.html)
 
 You can create and bind an instance to your application by using the Cloud Foundry CLI.
 

docs/docs/v4/connectors/redis.md

@@ -117,9 +117,9 @@ For a complete sample app that uses `IDistributedCache`, see https://github.com/
 
 This Connector supports the following service brokers:
 
-- [Tanzu for Valkey on Tanzu Platform](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-valkey-tanzu-platform/11-0/valkey-tp/index.html)
-- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-13/csb-azure/reference-azure-redis.html)
-- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-15/csb-aws/reference-aws-redis.html)
+- [Tanzu for Valkey on Cloud Foundry](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-valkey-tanzu-platform/11-0/valkey-tp/index.html)
+- [Tanzu Cloud Service Broker for Microsoft Azure](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-azure/1-15/csb-azure/reference-azure-redis.html)
+- [Tanzu Cloud Service Broker for AWS](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/cloud-service-broker-aws/1-17/csb-aws/reference-aws-redis.html)
 
 You can create and bind an instance to your application by using the Cloud Foundry CLI.
 

docs/docs/v4/security/index.md

@@ -1,6 +1,6 @@
 # Cloud Security
 
-Steeltoe provides several libraries that simplify using Cloud Foundry-based security services (such as [UAA Server](https://github.com/cloudfoundry/uaa), [Single Sign-On for VMware Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/index.html) and [instance identity certificates](https://docs.cloudfoundry.org/devguide/deploy-apps/instance-identity.html)) for authentication and authorization.
+Steeltoe provides several libraries that simplify using Cloud Foundry-based security services (such as [UAA Server](https://github.com/cloudfoundry/uaa), [Single Sign-On for Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/index.html) and [instance identity certificates](https://docs.cloudfoundry.org/devguide/deploy-apps/instance-identity.html)) for authentication and authorization.
 
 Choose from the following options when using Cloud Foundry security integration:
 

docs/docs/v4/security/jwt-bearer.md

@@ -1,6 +1,6 @@
 # Resource Protection using JWT in ASP.NET Core
 
-This library is a supplement to ASP.NET Core Security, adding functionality that helps you use Cloud Foundry Security services such as [Single Sign-On for VMware Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/index.html) or a [UAA Server](https://github.com/cloudfoundry/uaa) for authentication and authorization using JSON Web Tokens (JWT) in ASP.NET Core web applications.
+This library is a supplement to ASP.NET Core Security, adding functionality that helps you use Cloud Foundry Security services such as [Single Sign-On for Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/index.html) or a [UAA Server](https://github.com/cloudfoundry/uaa) for authentication and authorization using JSON Web Tokens (JWT) in ASP.NET Core web applications.
 
 For more information, see also the [Steeltoe Security samples](https://github.com/SteeltoeOSS/Samples/blob/4.x/Security/src/AuthWeb/README.md).
 
@@ -156,11 +156,11 @@ See the [Steeltoe Security samples](https://github.com/SteeltoeOSS/Samples/blob/
 * [Get the user's token](https://github.com/SteeltoeOSS/Samples/blob/4c0b222a8ea201240bb6b99aae46434864cf4dd1/Security/src/AuthWeb/Controllers/HomeController.cs#L60)
 * [Include the token in a downstream request](https://github.com/SteeltoeOSS/Samples/blob/4c0b222a8ea201240bb6b99aae46434864cf4dd1/Security/src/AuthWeb/ApiClients/JwtAuthorizationApiClient.cs#L24)
 
-### Single Sign-On for VMware Tanzu
+### Single Sign-On for Tanzu
 
-When using Single Sign-On for VMware Tanzu, you must choose a service plan before you create a service instance.
+When using Single Sign-On for Tanzu, you must choose a service plan before you create a service instance.
 If you do not have an existing service plan, a platform operator might need to create a new plan for you.
-For information about configuring service plans for use by developers, a platform operator should follow the steps in the [Single Sign-On for Tanzu operator guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/operator-index.html).
+For information about configuring service plans for use by developers, a platform operator should follow the steps in the [Single Sign-On for Tanzu operator guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/operator-index.html).
 
 After you have identified the service plan to use, create a service instance:
 
@@ -171,7 +171,7 @@ cf create-service p-identity your-plan sampleService
 #### Bind and configure with app manifest
 
 Using a manifest file when you deploy to Cloud Foundry is recommended, and can save some work with the SSO configuration.
-For information about configuring an app manifest, see the [Single Sign-On documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/config-apps.html#configure-app-manifest).
+For information about configuring an app manifest, see the [Single Sign-On documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/config-apps.html#configure-app-manifest).
 
 Consider this example manifest that names the application and buildpack, and configures properties for the SSO binding:
 
@@ -208,7 +208,7 @@ Then you can configure the SSO binding with the web interface.
 
 For more information, see:
 
-* the [Single Sign-On for Tanzu developer guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/developer-index.html)
+* the [Single Sign-On for Tanzu developer guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/developer-index.html)
 * the [Steeltoe Security samples](https://github.com/SteeltoeOSS/Samples/blob/4.x/Security/src/AuthWeb/README.md)
 
 ### UAA Server

docs/docs/v4/security/sso-open-id.md

@@ -2,7 +2,7 @@
 
 OpenID Connect is commonly used when users need to be able to interact with a collection of applications using a single set of credentials for authentication and authorization.
 
-This library is a supplement to ASP.NET Core Security's OpenID Connect library (`Microsoft.AspNetCore.Authentication.OpenIdConnect`), adding functionality that helps you use Cloud Foundry Security services such as [Single Sign-On for VMware Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/index.html) or [User Account and Authentication (UAA) Server](https://github.com/cloudfoundry/uaa).
+This library is a supplement to ASP.NET Core Security's OpenID Connect library (`Microsoft.AspNetCore.Authentication.OpenIdConnect`), adding functionality that helps you use Cloud Foundry Security services such as [Single Sign-On for Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/index.html) or [User Account and Authentication (UAA) Server](https://github.com/cloudfoundry/uaa).
 
 General guidance on the use of OpenID Connect is beyond the scope of this document; these resources are recommended:
 
@@ -175,11 +175,11 @@ The preceding example establishes the following security rules:
 >
 > See the [Steeltoe Security samples](https://github.com/SteeltoeOSS/Samples/blob/4.x/Security/src/AuthWeb/README.md) for examples of additional basic functionality, such as signing out of the application.
 
-### Single Sign-On for VMware Tanzu
+### Single Sign-On for Tanzu
 
-When using Single Sign-On for VMware Tanzu, you must choose a service plan before you create a service instance.
+When using Single Sign-On for Tanzu, you must choose a service plan before you create a service instance.
 If you do not have an existing service plan, a platform operator may need to create a new plan for you.
-For information about configuring service plans for use by developers, a platform operator should follow the steps in the [Single Sign-On for Tanzu operator guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/operator-index.html).
+For information about configuring service plans for use by developers, a platform operator should follow the steps in the [Single Sign-On for Tanzu operator guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/operator-index.html).
 
 After you have identified the service plan to use, create a service instance:
 
@@ -190,7 +190,7 @@ cf create-service p-identity your-plan sampleService
 #### Bind and configure with app manifest
 
 Using a manifest file when you deploy to Cloud Foundry is recommended, and can save some work with the SSO configuration.
-For information about configuring an app manifest, see the [Single Sign-On documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/config-apps.html#configure-app-manifest).
+For information about configuring an app manifest, see the [Single Sign-On documentation](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/config-apps.html#configure-app-manifest).
 
 Consider this example manifest that names the application and buildpack, and configures properties for the SSO binding:
 
@@ -228,7 +228,7 @@ Then you can configure the SSO binding with the web interface.
 
 For more information, see:
 
-* [Single Sign-On for Tanzu developer guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-16/sso/developer-index.html)
+* [Single Sign-On for Tanzu developer guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/single-sign-on/1-17/sso/developer-index.html)
 * [Steeltoe Security samples](https://github.com/SteeltoeOSS/Samples/blob/4.x/Security/src/AuthWeb/README.md).
 
 ### UAA Server

docs/docs/v4/welcome/whats-new.md

@@ -328,7 +328,7 @@ For more information, see the updated [Bootstrap documentation](../bootstrap/ind
 - New configuration provider to decrypt settings in Config Server (should be added as late as possible)
 - Reduced noise in Config Server logging
 - Universal configuration of client certificates, using ASP.NET Options pattern (named, with fallback to default)
-- Added support for reading from [Application Configuration Service for VMware Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-application-platform/1-12/tap/application-configuration-service-about.html) on Kubernetes
+- Added support for reading from [Application Configuration Service for Tanzu](https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-application-platform/1-12/tap/application-configuration-service-about.html) on Kubernetes
 - Improved support for ASP.NET Options pattern, responding to configuration changes at runtime
 - Removed configuration provider that directly interacts with the Kubernetes API