Docker Desktop OAuth2 should provide URL to user to login, unable to login using non-default OS open-browser #886
Description
It is not possible to login to Docker Desktop on Windows (maybe other platforms too) when the default browser is the wrong browser (a browser the user does not wish to login at login.docker.com with, because they use another browser for that purpose).
If a desktop application is using a website OAuth2 mechanism to authenticate, then it should make available to the user the login introduction/starting link to the user, such as copy it to the clipboard.
Many redirects occur during the preparation and login process to allow OAuth2 to complete as required.
Unfortunately by the time the link appears in the URL box to the user in a stable browser page (one that has finished loading after redirects) it has already lost the introduction/setup information. So the link the user sees can not be simply copied and pasted into the correct browser to complete the login.
The user then complete the login successfully, the webpage correctly shows logged in online at hub.docker.com. However the Docker Desktop Application does not show the state as logged in and still insists login is still needed.
Which service(s) is this request for?
Docker Desktop on Windows
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I am trying to login and it forces you to login.docker.com but the introduction link is lost.
Are you currently working around the issue?
Yes by skipping the login, I not login on docker on windows and use linux podman instead.
Additional context
I believe the problem can be solved, if the "Sign In" button at the top, has a right click action to copy the URL it is trying to load. Also the Notification item indicating you are not signed in, should also have a Copy Login URL link/button/action, which does the same thing more clearly informing the user.
When the button would copy the URL onto the clipboard (instead of sending it to the operating system to load in a browser). This way the user can then just open the browser they login with, and paste the link.
It is my understanding the introduction link might be to a localhost server that setups up the browser then immediately redirects to the login.docker.com using a different link, which then redirects back to localhost to inform Docker Desktop the process is complete. This chain is broken so login is not possible.