opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-29 01:02:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

Doc: Fix wrong default callback URL (#57908)

Browse Source 
* doc: fix wrong default callback URL

* doc: fix gitlab typos
This commit is contained in:
Jo
2022-10-31 15:13:27 +00:00
committed by GitHub
parent a59dc8b7ad
commit 07991c76fe
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sources/setup-grafana/configure-security/configure-authentication/github/index.md
View File

@ -23,9 +23,11 @@ settings page). When you create the application you will need to specify
a callback URL. Specify this as callback: a callback URL. Specify this as callback:
```bash ```bash
http://<my_grafana_server_name_or_ip>:<grafana_server_port>/grafana/login/github http://<my_grafana_server_name_or_ip>:<grafana_server_port>/login/github
``` ```
> Note: <my_grafana_server_name_or_ip>'s value should match your grafana server's `root_url`, the URL used to access grafana.
This callback URL must match the full HTTP address that you use in your This callback URL must match the full HTTP address that you use in your
browser to access Grafana, but with the suffix path of `/login/github`. browser to access Grafana, but with the suffix path of `/login/github`.
When the GitHub OAuth application is created you will get a Client ID and a When the GitHub OAuth application is created you will get a Client ID and a

6
docs/sources/setup-grafana/configure-security/configure-authentication/gitlab/index.md
View File

@ -33,10 +33,10 @@ 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 _read_api_as the_Scope_and submit the form. Note that if you're Finally, select `read_api` as the scope and submit the form. Note that if you're
not going to use GitLab groups for authorization (i.e. not setting not going to use GitLab groups for authorization (i.e. not setting
`allowed_groups`, see below), you can select_read_user_ instead of _read_api_as `allowed_groups`, see below), you can select `read_user` instead of `read_api` as
the_Scope_, thus giving a more restricted access to your GitLab API. 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 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