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

[Feature Request] Accessing the Cookies, that are received from API responses #810

Open
BorisBarbarossa opened this issue Apr 3, 2024 · 1 comment

Comments

@BorisBarbarossa
Copy link

Describe the bug

For the Authentication with my API, I need to send a jwt to a specific URL, which sends back a session cookie, that I have to put into the header of every further Get/Post request, that I send to the API. I wanted to save the session cookie in a variable, so that I can access it for every request. The problem is, that Grafana / the Infiniy Plug-in doesn’t let me access the cookie, which is sent in the header of the API response. I tried using the “result parsing options” like this: “result.headers[“set-cookie”]”, but it can only access the body of the response.

I would really appreciate the possibility to access and store the cookies, that are sent back, so that I can attach them in the header for my further requests, since this is how the Authentication is handled with the service I want to connect to.

Steps to reproduce

  1. Send a POST request to an API, that sends back an OK response with an empty body and a set-cookie header.
  2. Try to store said cookie.

Note: bugs will be fixed only if enough information provided to reproduce the issue

Screenshots

Screenshot 2024-03-28 085840
Screenshot 2024-03-28 085920

Version Details:

  • Grafana version : Grafana v11.0.0-68643
  • Plugin version : Infinity Plug-in V2.50
@yesoreyeram
Copy link
Collaborator

Hiya. Session cookie type of authentication is not supported yet and no immediate plans to support either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants