-
Notifications
You must be signed in to change notification settings - Fork 12.6k
Backend plugins: Unsigned external plugins should not be loaded by default #24027
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
Comments
@bergquist As I am quite new to Grafana I am unsure, but it would seem that the backend plugin tutorial does not account for this recent update. https://grafana.com/tutorials/build-a-data-source-backend-plugin/#3 Which I believe is now the cause of:
|
@Shannanigans thanks for reporting that, it does look as if it needs to be updated. Would you mind creating an issue for updating the tutorial? |
@aknuds1 Am I correct in assuming that the issue should be created in the tutorials repo? |
@Shannanigans That looks correct to me. BTW you can use the setting |
In case anyone lands here with a similar issue and is using docker you can add you plugin to the unsigned whitelist like so: docker run -d \
-p 3000:3000 \
-v "$(pwd)"/grafana-plugins:/var/lib/grafana/plugins \
--name=grafana \
-e "GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS=myorg-my-backend-data-source-plugin" \
grafana/grafana |
None of the above options work, whoever has this problem will have to add the environment variables like this: |
@LaurianoElmiroDuarte you're a lifesaver |
I found this topic yesterday, hugs
…On Fri, Aug 28, 2020 at 10:01 AM Jad Baz ***@***.***> wrote:
@LaurianoElmiroDuarte <https://github.com/LaurianoElmiroDuarte> you're a
lifesaver
It just so happens I'm actually looking for this exact plugin
Thanks a million!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24027 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBBWIQGRMMLT5DDTL63LI3SC6TBFANCNFSM4MTOJ3HQ>
.
|
@LaurianoElmiroDuarte How would I add those environment variables when running grafana installed on centos8? I am running into the same issue with it not loading the zabbix plugin, and like you, nothing I have tried from these forums has worked... Thoughts? Ideas? -JF |
do like this:
docker run -d -p 3000:3000 --name=grafana -e
"GF_INSTALL_PLUGINS=alexanderzobnin-zabbix-app" -e
"GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS=alexanderzobnin-zabbix-datasource"
-v dados:/var/lib/grafana grafana/grafana
…On Mon, Aug 31, 2020 at 3:39 PM Jeremy Felpel ***@***.***> wrote:
@LaurianoElmiroDuarte <https://github.com/LaurianoElmiroDuarte> How would
I add those environment variables when running grafana installed on centos8?
I am running into the same issue with it not loading the zabbix plugin,
and like you, nothing I have tried from these forums has worked...
Thoughts? Ideas?
-JF
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24027 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBBWIT43DUPI7W6KDBMBRTSDPU6XANCNFSM4MTOJ3HQ>
.
|
adding the following to /var/grafana/grafana.ini in the [plugins] section is how I did it on a non-docker install. Here is my log entry before making the change:
And after:
The datasource showed up after this. |
Any news about allowing the community to sign plugins? |
How to pass this command <-e "GF_INSTALL_PLUGINS = grafana-kubernetes-app" -e "GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS = grafana-kubernetes-app"> in Kubernetes grafana.yaml file |
Unsigned external plugins should not be loaded by default since it can be considered a security issue. Grafana should provide a setting to override this behavior for specified plugins.
External plugins means plugins installed into the plugins directory (configured via
paths.plugins
).EX
Note by Arve:
According to @ryantxu we should only validate the signatures of back-end plugins for now.
The text was updated successfully, but these errors were encountered: