-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
isAuth seems to be true even if not set in the panel editor #81
Comments
I'm also experiencing something strange
i have currently set the authentication switch off but it seems like the panel is still enforcing proper cors rules. |
i had similar problems. seems that this was fixed, but not republished: if (options.isAuth) {
fetchOpts.credentials = 'include';
requestHeaders.set('Authorization', 'Basic ' + btoa(options.username + ':' + options.password));
} Can someone just republish this? |
this is implemented in v7.0.25 but the published version (grafana.com) is v7.0.23. So any automated (e.g. via docker) or manual (via UI) fetches v7.0.23 by default. would be great, if someone can publish v7.0.25 @ grafana.com |
@derjust any chance we can republish to Grafana? Or is there a way someone else can? Would be great to use this. |
When I try to execute a REST call to my home assistant server I get the following error from the preflight request:
Credentials flag is true, but Access-Control-Allow-Credentials is not "true".
I have configured my home assistant server with the correct
cors_allowed_origins
I am using the following headers:Authorization: Bearer (my home assistant token)
Authentication switch is turned off and the request is a POST request with a valid json which works fine if I try it with another HTTP client.
The text was updated successfully, but these errors were encountered: