-
Notifications
You must be signed in to change notification settings - Fork 560
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
Oauth grant_type=password is inaccessible #629
Comments
This issue is stale because it has been open for 90 days with no |
/reopen |
/remove-lifecycle stale |
@jonjohnsonjr friendly ping on the PR for this: #1740 |
This issue is stale because it has been open for 90 days with no |
Before #628 we would fall back to the oauth flow for username/password if the token flow failed. This is not great behavior, since it almost always will fail, so we removed that fallback. As a result, there's actually no way to use username/password with the oauth flow.
Docker has a similar codepath that is reachable if the
ForceOAuth
option is set in theirTokenHandlerOptions
, but as far as I can tell there's no existing code that actually exercises that path in the docker client.It's unclear to me if any registries support this or any clients need it, and there's no easy way to tell if we should take that path from the registry response.
The text was updated successfully, but these errors were encountered: