-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
Bug (v5-beta1) GitHub Login #10823
Comments
Have you verified that the |
Yep, I've verified that. Those have not changed during the upgrade. 4.6 was stable with that configuration, the 5.0 beta is not. |
This seems to be related to the changes in #10112, specifically if your user is a member of a private GitHub org. I can lookup my user to get the organization URL:
Then if I curl the
It seems like we should be using GET /user/orgs instead of GET /user/:user/orgs. That way if you're running Grafana with a private GitHub org you can still login. |
* grafana/master: new dashboard is now hidden from viewer, fixes grafana#10815 (grafana#10854) fixed bg gradient, fixes grafana#10869 (grafana#10875) login: fix broken reset password form (grafana#10881) docs: spelling. dashboard: always make sure dashboard exist in dashboard acl http api (grafana#10856) Fix grafana#10823 (grafana#10851) provisioning: better variable naming provisioning: dont return error unless you want to cancel all operations provisioning: createWalkFn doesnt have to be attached to the filereader anymore provisioning: update sample config to use path provisioning: avoid caching and use updated field from db provisioning: delete dashboards before insert/update provisioning: fixed bug in saving dashboards. provisioning: delete dashboards from db when file is missing provisioning: enables title changes for dashboards dashboards: save provisioning meta data provisioing: add lookup table provisioned dashboards codestyle: extract code into methods
We've just updated from 4.6.3 to 5.0.0 beta 3 and GitHub authentication now results in the "User not a member of one of the required organizations". The configuration is supplied through environment variables and is unchanged from the previous version which authenticated successfully. |
@IngmarStein @torkelo I'll investigate it and fix in 24 hours |
Seeing same issue here with priv Github Org and 5.0.0-beta4 |
fix is coming in beta5 (or get it now in nightly build), reverted the #10823 change that caused the issue |
Just checked Grafana v5.0.0-beta4 (commit: 3964d6b) but still |
#11028 works. thx a lot |
I'm using the new v5 beta with the github auth plugin.
Here's our config:
When a user (who belongs to the github organization) attempts to login we receive:
I was able to get some info from the logs:
The text was updated successfully, but these errors were encountered: