This topic describes the changes in this minor release of Single Sign‑On for VMware Tanzu Application Service.
For product versions and upgrade paths, see Upgrade Planner.
Single Sign‑On v1.16 is a long-term supported (LTS) version. Single Sign‑On v1.16 is supported through April 2026.
Over the life cycle of Single Sign‑On v1.16, VMware releases security patches that occasionally include feature enhancements and maintenance updates.
For more information about Single Sign‑On v1.16 LTS, please contact your Account Team.
Release date: August 13, 2024
Upgrade to use cf-cli version 8.
As of v1.64.0 cf-cli v6 has been removed. This upgrade includes cf-cli v1.65.0
Spring Boot 3.3.2 Dependency Upgrade
Release date: April 25, 2024
Spring Boot 3.2.5 Dependency Upgrade
Release date: March 28, 2024
The 1.16.x release train is a modernization of the 1.14.x and 1.15.x branches. The tile requires the Ubuntu Jammy stemcell and Java 21 as a minimum runtime environment.
The 1.16.1 version has been tested on TAS 6.0, 5.0, 4.0, 3.0, 2.13 and 2.11.
The default buildpack, java_buildpack_offline
, has Java 21 in newer versions, including newer patch versions, of the Tanzu Application Service that include the v4.65+ of the Java Buildpack.
For installations that do not have an updated java_buildpack_offline
, the installer can set the value https://github.com/cloudfoundry/java-buildpack
under Property Configurations in Tanzu Operations Manager for the latest Java Buildpack to be used.
The SSO Tile runs as 4 separate microservices in the system
org and the identity-service-space
space:
identity-service-broker
sso-api
sso-operator-dashboard
sso-developer-dashboard
cf target -o system -s identity-service-space
cf apps
name requested state processes routes
identity-service-broker started web:2/2 p-identity-broker.sys.demo.cf-app.com
sso-api started web:2/2 sso-api.sys.demo.cf-app.com
sso-developer-dashboard started web:2/2 p-identity.sys.demo.cf-app.com/developer
sso-operator-dashboard started web:2/2 p-identity.sys.demo.cf-app.com
During the installation, a green-blue deploy strategy is used (example for sso-operator-dashboard):
green
prefix, in this example green-sso-operator-dashboard
.green
prefix, for example: green-sso-operator-dashboard.sys.demo.cf-app.com.cold
as a suffix: sso-operator-dashboard
-> sso-operator-dashboard-cold
.green
: green-sso-operator-dashboard
-> sso-operator-dashboard
.At the end of the installation, you will have the 8 total microservices, 4 of them running and the other 4 from the previous version paused with no running processes.
cf target -o system -s identity-service-space
cf apps
name requested state processes routes
identity-service-broker started web:2/2 green-identity-service-broker.sys.demo.cf-app.com, p-identity-broker.sys.demo.cf-app.com
identity-service-broker-cold stopped web:0/2 green-identity-service-broker.sys.demo.cf-app.com
sso-api started web:2/2 sso-api.sys.demo.cf-app.com
sso-api-cold stopped web:0/2
sso-developer-dashboard started web:2/2 green-sso-developer-dashboard.sys.demo.cf-app.com, p-identity.sys.demo.cf-app.com/developer
sso-developer-dashboard-cold stopped web:0/2 green-sso-developer-dashboard.sys.demo.cf-app.com
sso-operator-dashboard started web:2/2 green-sso-operator-dashboard.sys.demo.cf-app.com, p-identity.sys.demo.cf-app.com
sso-operator-dashboard-cold stopped web:0/2 green-sso-operator-dashboard.sys.demo.cf-app.com
Support changes:
Dependency upgrades in this release: