Maurice Faber

tnx for helping out...I was wondering the same thing. The auth header is set by keycloak and all other internal services that act as client to it have no issues....

I now see one cluster that has no issues with exactly the same setup as on a duplicate cluster I created. One is allowing the login now fine, the other...

so at first I thought the logs were relevant, but the working setup logs exactly the same lines, even though auth works: ``` core 2021-07-05T20:15:40Z [ERROR] [/server/middleware/security/oidc_cli.go:62][requestID="de6b09e5-ce00-4369-a4d6-4a08054a72ce"]: failed to verify...

Let me also diff the logs in the registry for completeness: The failing registry: ``` time="2021-07-05T20:19:08.125619711Z" level=error msg="error authenticating user "admin": authentication failure" go.version=go1.15.12 http.request.host=harbor.xxxxx http.request.id=d02c594b-1180-41fb-8dd1-ee633a1fd7a3 http.request.method=GET http.request.remoteaddr=127.0.0.1 http.request.uri="/v2/" http.request.useragent="docker/20.10.6...

Another observation: On the cluster where I am able to successfully `docker login` with the token, a pullSecret created with the same information is NOT working.

We have been spending quite some time on figuring this out. The last two lines you mentioned seem to just be noise because of the software design flaw ("trying" a...

> docker login failure issue (with oidc enabled) seems to be resolved for 2.4 release! not working for us ;( On `v2.4.0` We see the following output after trying to...

Using the same external IDP., on an AWS cluster we see no problems, but on AKS we do. Probably a coincidence. But, more interesting, after disabling OIDC we see the...

I ditched it in favor of an nginx-proxy fork with proxyprotocol support

If I do this linting and completion works: ```yaml from interpreter import Interpreter interpreter = Interpreter() ``` but I get execution error: ``` ImportError: cannot import name 'Interpreter' from ''...