IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-11-25 10:20:29 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: gitlab: add note about more restrictive API scope

Browse Source 
If `allowed_groups` is not used with GitLab authentication, the
*read_user* scope can be used instead of *api*.
This commit is contained in:
Benoît Knecht 2018-08-14 14:09:04 +02:00
parent ce804e9981
commit 5a91e670d8
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/sources/installation/configuration.md
View File

@ -448,8 +448,12 @@ instance, if you access Grafana at `http://203.0.113.31:3000`, you should use
http://203.0.113.31:3000/login/gitlab http://203.0.113.31:3000/login/gitlab
``` ```
Finally, select *api* as the *Scope* and submit the form. You'll get an Finally, select *api* as the *Scope* and submit the form. Note that if you're
*Application Id* and a *Secret* in return; we'll call them not going to use GitLab groups for authorization (i.e. not setting
`allowed_groups`, see below), you can select *read_user* instead of *api* as
the *Scope*, thus giving a more restricted access to your GitLab API.
You'll get an *Application Id* and a *Secret* in return; we'll call them
`GITLAB_APPLICATION_ID` and `GITLAB_SECRET` respectively for the rest of this `GITLAB_APPLICATION_ID` and `GITLAB_SECRET` respectively for the rest of this
section. section.