Skip to content
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

Problem when using keystone auth mode and server(proxy) access mode #68

Open
rocasyeh opened this issue Jan 17, 2019 · 3 comments
Open

Comments

@rocasyeh
Copy link

When using token auth mode and server access mode, test operation will get gnocchi resources through grafana server normally.
However, if using keystone auth mode, test operation will get token through proxy but get gnocchi resource directly.
For example (in one test operation):
http://<grafana_ip>:<grafana_port>/api/datasources/proxy/5/v3/auth/tokens
http://<gnocchi_ip>:8041/v1/resource

@rocasyeh
Copy link
Author

btw, keystone's ip and gnocchi's ip are the same

@ki4rbc
Copy link

ki4rbc commented Jun 7, 2019

@rocasyeh,

I'm seeing the same thing as well. When I do a tcpdump of all traffic from the grafana host to the controller, home of keystone and gnocchi, i only see a successful authentication reply with a token and endpoint catalog. I never see an attempt to the gnocchi api on port 8041. In my case, Cross-Origin Resource Sharing is configured and tested even though is likely not an issue in server access mode.

@sileht Mr. Abaakouk, any thoughts?

@JochenFriedrich
Copy link

I can confirm the problem, as well.
In proxy mode, parsing the service catalog is of no use as you can only connect to the configured endpoint, anyways.
So I replaced the parsing code with a simple:

_this.url = _this.keystone_endpoint;

This makes it work ok for me in proxy mode. It won't work in direct mode, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants