DOCS: Updated GitLab Authentication Callback URL

- Removed trailing slash from Callback URL which caused failure
- Adjusted to https://YourSonarQubeURL.com to https://sonarqube.mycompany.com/ to be consistent with Github/SAML docs

diff --git a/server/sonar-docs/src/pages/instance-administration/delegated-auth.md b/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
index b5fca7c032d8fdbcdd416c3184a65e12d0f5d6ee..f68bd73ad9826130f413ea9365054e65768c49a3 100644 (file)
--- a/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
+++ b/server/sonar-docs/src/pages/instance-administration/delegated-auth.md
@@ -59,7 +59,7 @@ You can delegate authentication to GitLab using a dedicated GitLab OAuth applica
 Create a GitLab OAuth application from your GitLab account. Click [here](https://docs.gitlab.com/ee/integration/oauth_provider.html) for general instructions.
 
    1. In the **Name** text box, name your app SonarQube.
-   1. In the **Redirect URI** text box, enter your SonarQube URL with the path `/oauth2/callback/gitlab/`. For example, `https://YourSonarQubeURL.com/oauth2/callback/gitlab/`.
+   1. In the **Redirect URI** text box, enter your SonarQube URL with the path `/oauth2/callback/gitlab`. For example, `https://sonarqube.mycompany.com/oauth2/callback/gitlab`.
    1. Under **Scopes**, select **api**.
 
 After saving your application, GitLab gives you your **Application ID** and **Secret**. Keep these at hand, open your SonarQube instance, and navigate to **[Administration > Configuration > General Settings > Security](/#sonarqube-admin#/admin/settings?category=security/)** to finish setting up GitLab authentication: