From a2cacac0e5cd92240d64fe120cd91f1e527f6613 Mon Sep 17 00:00:00 2001
From: Kaligule <Code@schauderbasis.de>
Date: Sun, 17 Jun 2018 14:45:41 +0200
Subject: [PATCH] Fix indentation in config example (#1447)

---
 .../site/content/docs/authentication-backends.md   | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/site/content/docs/authentication-backends.md b/website/site/content/docs/authentication-backends.md
index 5ff302fc..91a001e6 100644
--- a/website/site/content/docs/authentication-backends.md
+++ b/website/site/content/docs/authentication-backends.md
@@ -101,13 +101,13 @@ With GitLab's Implicit Grant, users can authenticate with GitLab directly from t
 
     ```yaml
     backend:
-    name: gitlab
-    repo: owner-name/repo-name # Path to your GitLab repository
-    auth_type: implicit # Required for implicit grant
-    app_id: your-app-id # Application ID from your GitLab settings
-    api_root: https://my-hosted-gitlab-instance.com/api/v4
-    base_url: https://my-hosted-gitlab-instance.com
-    auth_endpoint: oauth/authorize
+      name: gitlab
+      repo: owner-name/repo-name # Path to your GitLab repository
+      auth_type: implicit # Required for implicit grant
+      app_id: your-app-id # Application ID from your GitLab settings
+      api_root: https://my-hosted-gitlab-instance.com/api/v4
+      base_url: https://my-hosted-gitlab-instance.com
+      auth_endpoint: oauth/authorize
     ```
 
 Note that in both cases, GitLab will also provide you with a client secret. You should _never_ store this in your repo or reveal it in the client.