-
Notifications
You must be signed in to change notification settings - Fork 23
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
Issue Keystone Auth, forcing HTTPS #49
Comments
Recent Chrome and Firefox are stricter about ssl. You can't mix non-ssl with ssl endpoint within the same page with CORS. So I don't think this can be solved on the plugin side. Maybe you should just ensure keystone AND Gnocchi are both in https:// Can you provide browser console output when the issue occurs ? so I can confirm my though. |
All connections are HTTP, Grafana, Keystone and Gnocchi. Endpoint Gnocchi is also set as HTTP. In Firefox, directly queries to HTTPS, while Chrome does HTTP but then redirect 307 to HTTPS. Tomorrow I'll send some screenshots. |
Console outputs:
|
Same problems. |
Using Auth Mode keystone, with all settings OK (URL endpoint http://controller:5000, domain, project, user and password) and CORS enabled.
Grafana gets the Keystone token and the Gnocchi endpoint, and goes to query it.
But, the connection is done via HTTPS automatically forced, not HTTP.
As HTTPS is not responding, data load fails.
This happens in some versions of Firefox and Chrome, Internet Explorer is not having this issue and gets the data OK.
The text was updated successfully, but these errors were encountered: