-
Notifications
You must be signed in to change notification settings - Fork 84
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
HTTP Authentication no longer works after enabling oauth #88
Comments
/CC @lucamilanesio |
Yeah, that is something specific to Ver. 2.14: HTTP Digest Auth isn't there anymore and all authentications are specific to the provider. I recall, however, we introduced a policy to still allow standard HTTP passwords, isn't it? |
What was that policy exactly? Or should the provider now implement itself OAuth-token based authentication, like cfoauth plugin is doing? |
There you go: https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#auth.gitBasicAuthPolicy |
Thanks, I think I understand now what happened. To rectify #84, i added So the solution is as easy as: adding this option to the
We should add this to the plugin documentation and FAQ. Will do it later, and let this issue open for a while. |
Thanks @davido and @lucamilanesio for the quick turnaround. I can confirm that adding that option fixed the issue for me. |
@fastest963 we shouldn't discuss Gerrit issues on GitHub though: typically all the issues are discussed on the Gerrit issue tracker or the mailing list. |
@lucamilanesio I had thought that this plugin was the issue, I didn't realize the followup comments that it was a gerrit issue. The error made it seem like this plugin didn't support HTTP authentication for git requests and I saw that there was a change in #84 specifically that added that error message that I was seeing. |
@fastest963 this plugin is on Gerrit Code Review as well (https://gerrit.googlesource.com/plugins/oauth) :-) This is simply the original repo where it was developed and is not the master "source of truth anymore" |
@lucamilanesio oops! Didn't see that. I just found the plugin by searching google. Thanks for the info. |
Btw ... I've created an issue on Gerrit => https://bugs.chromium.org/p/gerrit/issues/detail?id=6034 |
When migrating to Gerrit 2.14, users on LDAP and OAuth want to be aware that a decision needs to be made on whether the Gerrit HTTP password should be used or not during Git/HTTP authentication. Not making any choice during upgrade, would have the effect of just using the default value, which may not be compatible with the user's needs and expectations, leading to failures after upgrade. This is what happened to early adopter of Gerrit 2.14 + OAuth: davido/gerrit-oauth-provider#88 Bug: Issue 6034 Change-Id: Iaa6677e95cc1a3e88e9987fc226abefe26603587
The issue listed above was merged and so this should be closed. |
We we're trying out 2.14.x and after setting auth=OAUTH we now get the following error when users try to HTTP authenticate with their git clients:
The text was updated successfully, but these errors were encountered: