API generated kubeconfig fails with a 401 error
search cancel

API generated kubeconfig fails with a 401 error

book

Article ID: 407640

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

When using a kubeconfig that was generated via TCA-M's API for token based authentication for SSO users, a 401 Unauthorized message is received.

Environment

3.2

Cause

vCenter is no longer connected to TCA-M.

Resolution

  1. Log into TCA-M's admin page at http://<TCA-M_FQDN>:9443
  2. Confirm the username/password for vCenter are correct, and that the status is 'green'.
  3. Retry the operation using the generated kubeconfig.