When accessing the SDDC Manager tab within the VCF Operations UI, or navigating to Fleet Management > Lifecycle, you observe the following:
Authorization Error: Unauthorized access.VCF Operations 9.x
token_signing_key.json file, located in /etc/vmware/vcf/commonsvcs/ on the SDDC Manager, has become corrupted or is 0-bytes.JSON Web Keys (JWK) necessary for secure communication between VCF Operations and SDDC Manager. When corrupted, the authentication handshake fails.To manually resolve the authorization error in existing environments, follow these steps to push valid keys from VCF Operations to the SDDC Manager:
vcf user and switch to root.cd /etc/vmware/vcf/commonsvcs/
mv token_signing_key.json token_signing_key.json.bak750: chmod 750 /etc/vmware/vcf/commonsvcs/curl -k https://<VCF_OPS_FQDN>/suite-api/.well-known/openid-configuration Command Output
{"issuer":"vcf_ops-#########-####-####-####-#############","jwks_uri":"https://<VCF-OPS-Primary-fqdn>/suite-api/jwks"}
Command Output
{"keys":[{"kty":"RSA","e":"AQAB","kid":"####################################"}]}
<SSO_PASSWORD> and <SDDC_MGR_FQDN>): token=$(curl -X POST -H "Content-Type: application/json" -d '{"username": "[email protected]","password": "<SSO_PASSWORD>"}' --insecure https://<SDDC_MGR_FQDN>/v1/tokens | jq -r '.accessToken')
curl -k -X POST 'https://<sddc-manager>/v1/tokens/signing-keys' -H "Content-Type: application/json" -H "Authorization: Bearer $token" -d '{"issuer":"vcf_ops-#########-####-####-####-#############","keys":[{"kty":"RSA","e":"AQAB","kid":"####################################"}]}'curl -X GET -H "Authorization: Bearer $token" --insecure https://<SDDC_MGR_FQDN>/v1/tokens/signing-keys | json_pp/etc/vmware/vcf/commonsvcs/token_signing_key.json has been automatically recreated and populated on the SDDC Manager filesystem.