-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: problems with bearer authentication #2096
Comments
logs with podman client and service set to the same as
same but with docker cli client
docker client with empty service. i havent included a log from podman because it can't handle empty service.
|
|
@peusebiu can you pls check if we could handle/fail this more gracefully. {"level":"info","module":"http","clientIP":"172.22.0.1:49190","method":"GET","path":"/v2/","statusCode":401,"latency":"0s","bodySize":283,"headers":{"Accept-Encoding":["gzip"],"Connection":["close"],"Docker-Distribution-Api-Version":["registry/2.0"],"User-Agent":["containers/5.23.1 (github.com/containers/image)"]},"goroutine":51,"caller":"zotregistry.io/zot/pkg/api/session.go:131","time":"2023-11-30T12:12:20.421826473Z","message":"HTTP API"} |
@nyabla can you give us the exact steps both on authentik and zot so that we can reproduce this panic? Understood that this is an operator error, but still in our opinion best if we handle this. |
@nyabla I tried to reproduce but I can't configure authentik, mainly I can not do the initial setup, it's prompting me to login with user and pass, instead of a prompt with setting up the admin account. Tried to add a username and password in .env config but same issue. |
Closing this, pls re-open if needed. |
Discussed in #2089
Originally posted by nyabla November 29, 2023
versions I tried on: 1.4.3 and 2.0.0-rc7
my config file: config.json
background: i am trying to run an instance of zot with authentication handled by authentik. i have a sort of proxy in front of the token endpoint of authentik in order to translate the
GET
token request into aPOST
request. The clients I tried (docker cli and podman) are both able to obtain a valid token from this endpoint.problem: zot gives a
500 Internal Server Error
response upon receiving a request with a (valid) bearer token ONLY when theservice
key underbearer
is non-empty. if theservice
key has an empty string (""
) then podman/skopeo get confused.what i tried: making sure that the value of the
aud
key in the jwt matches the value ofservice
, similarly to the auth.docker.io endpoint.The text was updated successfully, but these errors were encountered: