Background

In THREESCALE-12007 , it was noted that Unicorn logs can leak access tokens in the log.

To resolve this, operator changes were applied to modify the startup command.

Issue

In a new 3scale 2.16 installation, this change is applied correctly and Unicorn logs do not leak access tokens.

However, if the installation is upgraded from 2.15, the container startup does not appear to be modified, and Unicorn logs continue to leak access tokens.

Workaround

1. Delete the system-app deployment
2. Allow the operator to recreate the deployment

Once the deployment is recreated, the startup command is modified, and the token leak no longer occurs.

Attached Files

Deployment file that results in token leak: 216_system_app_post_upgrade.yaml

Deployment file that resolves token leak: 216_system_app_post_recreate.yaml