Failed logins to TAC/Bitnami Secure private registry when using Nexus server as proxy-cache

Products

• VMware Tanzu Application Catalog

Issue/Introduction

• You need to login to our TAC private registry from your on-prem Nexus server, which serves as a proxy-cache.
• The Nexus team is supplying "_json_key" for the user and the JSON file's "private key" field for the password.
• You get the following error when trying to pull from the Nexus to the TAC catalog: 
  
  Error response from daemon: manifest for nexus_server.domain.com:18095/vmw-app-catalog/hosted-registry-###########/containers/debian-11/<package_name> not found: manifest unknown: manifest unknown
  
  
• In Nexus proxy-cache logging, you might see errors like:
  
  Failed to retrieve docker bearer token
BEARER [complete=true] authentication error: Could not retrieve token from https://repo_name.pkg.dev/v2/token. Status code: 401
  
  
• Using the same credentials, you are able to log into the private registry on TAC/Bitnami Secure directly.

Cause

This failure is caused by a bug in Nexus proxy-cache. Please open a ticket with Nexus for assistance.

Resolution

Open support ticket with Nexus for assistance correcting this.