You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We use nginx to proxy harbor,the harbor is deploy at http and the nginx is over https,
when client request pull or push ,the harbor response fail with 401 code, and the response header Www-Authenticate content is like realm="http://<hostname>:<port>/service/token",so the client has to request the token over http
Describe the solution you'd like
I wish to config the realm url with harbor.yml
The text was updated successfully, but these errors were encountered:
We use Gateway In front of harbor,so the harbor is just config by http, and the realm is always return the http url, we want to custom config the realm url but it was not support
The realm (service token url) is the same as <externalURL>/service/token, if you want to change it you could customize it in the harbor.yaml or values.yaml
Is your feature request related to a problem? Please describe.
We use nginx to proxy harbor,the harbor is deploy at http and the nginx is over https,
when client request pull or push ,the harbor response fail with
401
code, and the response headerWww-Authenticate
content is likerealm="http://<hostname>:<port>/service/token"
,so the client has to request the token overhttp
Describe the solution you'd like
I wish to config the realm url with
harbor.yml
The text was updated successfully, but these errors were encountered: