Token authentication

[igoras1993]

Is your feature request related to a problem? Please describe.
In Docker registry V2, a preferred way to authenticate is using a Central Auth architecture. This is described here. An authorization protocol is actually simple and straight forward:

1. Perform ordinary request to docker registry
2. If getting 401 response code, look for WWW-Authenticate header, extracting realm and scope parameters.
3. Perform a GET request:
   3.1. Use address given in realm,
   3.2. Send scope along with parameters,
   3.3. Use Basic Authentication to pass username and password
4. Obtain token from the response
5. Resend original request to docker registry, but this time place obtained token in Authentication: Bearer <...> header.
6. If given token authorizes client to a given resource, docker registry will return correct response.

This is a very general and powerful way for doing authentication. It strongly separates registry app from the auth part. Client's responsibility is only to follow protocol and supply username and password in 3.3. step.

Would You mind to implement this kind of protocol in Your UI project?

Describe the solution you'd like
Actually, the simplest algorithm I can imagine will look like this:

1. Every time experiencing 401 from DR, display a login form for user
2. Follow step 3. from authentication protocol
3. Use obtained token in Authentication: Bearer <...> header in future requests.

Describe alternatives you've considered
A more general way involves playing with refresh tokens, which of course is also possible.

[Joxit]

Hello,

Thank you for your feature request :) I'm supporting only basic auth because it was the easiest way.
Token authentication can be interesting, so I try to do something but there will be no guarantee

[Joxit]

Will be release in 2.0.0 🚀

[nhoudement-pro]

Hello,
I'm actually trying to use your ui with a private registry configured with token authentication.
To handle token authentication, I'm using docker_auth.
Both registry and docker_auth are running into their respective containers as well as registry-ui and all 3 containers are running on the same host.
Token authentication has been set to allow anonymous users to pull images from the registry (few accounts are allowed to push on the registry).
When I access registry-ui web interface, it receives the authentication challenge from the registry (because I can see the "popup" on the bottom right corner of the web page, but it is not able to display the content of the registry and it doesn't display a popup so that I can input some credentials.
Below, the versions of the components used:
registry : 2.7.0
docker_auth: 1.9.0
registry-ui: 2.1.0

Can you please help me to solve this issue ?

Thank you very much.

[Cronist]

I am one of the guys waiting for token auth released for UI too. still pending.