-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support API requests from service accounts #25
Conversation
* Support auth from Authorization header * First cookies will be checked, if not found, Auth header will be checked * If any of them are successful, headers will be forwarded for client reqs Signed-off-by: Mahendra Paipuri <[email protected]>
@mahendrapaipuri
I get the following error:
is there something i might have done wrong? ps: the auth with service account is working correctly against che grafana server (I tried it against the dashboards API) |
@and-mora Not the You will need to download the artifacts from CI. Regarding the error you are getting
You will need to provision the plugin with proper settings. Grafana related config parameters cannot be configured from UI. The error is saying Grafana's App URL is not found which is normally |
I just mentioned the name inside the plugin-artifact.zip that I downloaded from the ci action.
You're right, I haven't replicated correctly the test environment. Now i think i fixed it.
|
@and-mora Awesome !! Cheers for testing. Appreciate it!
Oh yes, that is true. Probably we should use a branch specific name in CI to better communicate what we are testing |
Sorry @mahendrapaipuri, maybe I miss-formulated the previous message. The plugin is still not working and returns 401 when I call it with curl. What I pointed out as working were the other tests I made (plugin with session cookie browser and dashboard API) before testing the plugin itself. |
Sorry, I havent looked at the logs keenly. How are you generating the token? Does token has viewer role?
This line indicates that token does not have permissions to view that dashboard. So you need to verify the permissions on the token you are using to make the request I tested it using the docker-compose included in the repo and it worked. What I did is:
|
Closes #24