-
Notifications
You must be signed in to change notification settings - Fork 2.1k
auth: add support for oauth device-code login #5344
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
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fcfdd7b
auth: add support for oauth device-code login
laurazard 6e4818e
Refactor `cli/command/registry`
laurazard e662467
login: normalize `registry-1.docker.io`
laurazard 5eb3275
filestore: don't print warning multiple times
laurazard c3fe7bc
fallback to regular login if oauth login fails to start
laurazard File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think this is new, but we're now using it twice; wondering if we're missing a new check for
isDefaultRegistryafter the above branch does acredentials.ConvertToHostname(serverAddress)(unrelated: I think the intent of
ConvertToHostnameis effectively "normalise storage key" - we need to look at some of that at some point - naming is confusing, and not always properly describes intent)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so? But we could dig into that after this. Much like
command/registry/login.go, this could use a bit of a cleanup.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On another look, I guess a user could try to logout by doing
docker logout index.docker.ioand we should make that work.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's roughly the scenario I had in mind. Technically it could go even further (log out for
[http(s)://]registry-1.docker.ioetc), but it looks like the current code only assumes "no registry" passed to mean docker hub. For the old code that made no real difference, as in that case it would at most do too many logouts (hostnameAddress, "http://"+hostnameAddress, "https://"+hostnameAddress), but for the new flow, it may be relevant that we would miss themanager.NewManager(store).Logout()call.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I started looking into this, and the current situation is – the web-based flow only triggers when the user runs either:
docker login, ordocker login https://index.docker.io/v1/the following do not work:
docker login index.docker.iodocker login https://index.docker.ioFor logout, the following trigger an oauth logout:
docker logout, ordocker logout https://index.docker.io/v1/This seems consistent to me, but WDYT @thaJeztah?