-
Notifications
You must be signed in to change notification settings - Fork 175
Description
Summary
I am not able to add a private repository that requires client authentication using certificates as a global/project repository. The public and private certificate were added as a new credential, but after talking with the repository owner it appears that the certificate information is not being passed to the repository.
The error that is returned:
Operation for registry https://privateRepo.privateDomain:443 failed: Ping attempts failed with errors: Service https://privateRepo.privateDomain:443/v1/ping returned error 403 for GET. id 77301 -- Service https://privateRepo.privateDomain:443/auth?service=https://privateRepo.privateDomain:443&scope=registry:catalog:* returned error 401 for GET. id 77303
I was able to validate that the certificate is valid and can connect to the repository because using the cert I was able to obtain a token using https://privateRepo.privateDomain:443/auth?service=https://privateRepo.privateDomain:443&scope=registry:catalog:*
Environment information
vSphere and vCenter Server version
vSphere version: 7.0.0 build 16749670
vCenter version: 7.0.0.10600
VIC version
VIC version: v1.5.5-7767-a7161963
VCH configuration
n/a
Details
Steps to reproduce
Actual behavior
Expected behavior
Logs
See also
Troubleshooting attempted
- Searched GitHub for existing issues. (Mention any similar issues under "See also", above.)
- Searched the documentation for relevant troubleshooting guidance.
-- https://vmware.github.io/vic-product/assets/files/html/1.5/vic_cloud_admin/working_with_registries.html
-- https://vmware.github.io/vic-product/assets/files/html/1.5/vic_cloud_admin/add_repos_in_portal.html - Searched for a relevant VMware KB article.