Commit 62870a0e authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'docs/omniauth-fix-link' into 'master'

Fix markdown link in Omniauth docs

See merge request !9082
parents 5849e90d 1352a80f
......@@ -89,4 +89,4 @@ user to sign in and authorize the GitLab application. If everything goes well
the user will be returned to GitLab and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -84,4 +84,4 @@ To enable the Microsoft Azure OAuth2 OmniAuth provider you must register your ap
On the sign in page there should now be a Microsoft icon below the regular sign in form. Click the icon to begin the authentication process. Microsoft will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -64,5 +64,5 @@ To enable the CAS OmniAuth provider you must register your application with your
On the sign in page there should now be a CAS tab in the sign in form.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -59,5 +59,5 @@ To enable the Crowd OmniAuth provider you must register your application with Cr
On the sign in page there should now be a Crowd tab in the sign in form.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -98,4 +98,4 @@ something else descriptive.
On the sign in page there should now be a Facebook icon below the regular sign in form. Click the icon to begin the authentication process. Facebook will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -111,4 +111,4 @@ Click the icon to begin the authentication process. GitHub will ask the user to
If everything goes well the user will be returned to GitLab and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -85,4 +85,4 @@ Click the icon to begin the authentication process. GitLab.com will ask the user
If everything goes well the user will be returned to your GitLab instance and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -90,4 +90,4 @@ At this point, when users first try to authenticate to your GitLab installation
1. Add any additional information as you wish - homepage, logo, privacy policy, etc. None of this is required, but it may help your users.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -317,4 +317,4 @@ Make sure that one of the above described scenarios is valid, or the requests wi
fail with one of the mentioned errors.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -124,4 +124,4 @@ you will not get a shibboleth session!
```
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
......@@ -80,4 +80,4 @@ To enable the Twitter OmniAuth provider you must register your application with
On the sign in page there should now be a Twitter icon below the regular sign in form. Click the icon to begin the authentication process. Twitter will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in.
[reconfigure]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure
[restart]: ../administration/restart_gitlab.md#installations-from-source
[restart GitLab]: ../administration/restart_gitlab.md#installations-from-source
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment