Routing-API Protocol “HTTPS only” Compatibility for TPCF 6.0 + 7.0 + 8.0

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Historically there have been both HTTP and HTTPS endpoints Routing-API.  In an effort to make the entire TPCF ecosystem more secure by default we want to remove the HTTP Routing-API endpoint. Below is the timeline for migrating all clients to using the HTTPS endpoint and removing the HTTP Routing-API endpoint.

Resolution

Timeline

• Prior to TPCF 6.0: HTTP and HTTPS Routing API endpoints are both available for clients to use.
• In TPCF 6.0: There is a new API-only property “Routing API Endpoint Protocol” with options for “HTTPS and plain HTTP” or “HTTPS only”. The default is “HTTPS and plain HTTP”. This property was intended to be used by clients to do compatibility testing with.
• All tiles with Routing API clients have been updated to use the HTTPS Routing API endpoint (see table for versions below).
• In TPCF 7.0: In the “Networking” tab the property “Routing API Endpoint Protocol” with options for “HTTPS and plain HTTP” or “HTTPS only” is now exposed in the UI. The default for upgrades and new installs is now “HTTPS only”. 
• In TPCF 8.0: The “Routing API Endpoint Protocol” property will be removed. The Routing API endpoint will only be available via HTTPS.

 

Tile	Version Compatible with Routing API via HTTPS
VMware Tanzu RabbitMQ for Tanzu Application Service	2.3.0