public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed some formatting issues for PRs from yesterday. (#33078) (#33079)

Browse Source
This commit is contained in:
achatterjee-grafana
2021-04-16 13:13:06 -04:00
committed by GitHub
parent 4106856569
commit 5bcc482697
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/administration/security.md
+2 -2
View File
@@ -37,9 +37,9 @@ To address this vulnerability, you can restrict data source query access in the
- Create multiple data sources with some restrictions added in data source configuration that restrict access (like database name or credentials). Then use the [Data Source Permissions]({{< relref "../permissions/datasource_permissions.md" >}}) Enterprise feature to restrict user access to the data source in Grafana.
- Create a separate Grafana organization, and in that organization, create a separate data source. Make sure the data source has some option/user/credentials setting that limits access to a subset of the data. Not all data sources have an option to limit access.
## Implications of enabling `Anonymous` access to dashboards
## Implications of enabling anonymous access to dashboards
When you enable Anonymous access to a dashboard, it is publicly available. This section lists the security implications of enabling Anonymous access.
When you enable anonymous access to a dashboard, it is publicly available. This section lists the security implications of enabling Anonymous access.
- Anyone with the URL can access the dashboard.
- Anyone can make view calls to the API and list all folders, dashboards, and data sources.