401 error while pushing since 1.2.11 about lstags

[ivanilves]

Please forgive me this long delay. I had a lot of involvement with sick kids and so on. 😓

I've released https://github.com/ivanilves/lstags/releases/tag/v1.2.14

So you can force BASIC auth by adding a parameter:

-B external.docker.mamdev.server.lan username:password

Still I fail to understand what was really broken since 1.2.11.

But here we just try to see if an issue could at least worked around 🤷‍♂️

[nudgegoonies]

No problem. I was ill too. Since yesterday i started homeoffice. Yes, with the parameter it works.

[nudgegoonies]

My team-lead and i discussed today about the authentication problem since 1.2.11.

It seems that lstags constructs a jwt token altough Artifactory has responded with a plain token.

Please have a look at my team-leads comments in this containerd issue:
containerd/containerd#3556 (comment)
containerd/containerd#3556 (comment)

See also these docker links:
https://docs.docker.com/registry/spec/auth/token/

jwt is an optional token method for docker registries:
https://docs.docker.com/registry/spec/auth/jwt/

[ivanilves]

Thank you very much for this input! lstags has always respected the remote registry authentication preferences and the only thing I could potentially blame here is my connection cache addition somehow messed up its decision making. Need to play more with Artifactory on my local PC to understand it... 😄

[ivanilves]

Thanks for this info! I demoted 1.2.11 to "pre-release", so latest would be 1.2.10 again.

Hope to have some time in nearest future to investigate this.

[nudgegoonies]

Thank you. We reverted to 1.2.10.

[cablespaghetti]

This also seems to be an issue on ECR. Downgrading to 1.2.10 fixes it.