summaryrefslogtreecommitdiff
path: root/doc/integration/openid_connect_provider.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-09-30 06:06:02 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-09-30 06:06:02 +0000
commit42572f63eab5db8dc39279e0deeeadef86180a71 (patch)
treeceab7f3103ae2a6b271ea219eac141adb61ff762 /doc/integration/openid_connect_provider.md
parente8185569bf058dde3f878b2a6be29649d3bcd49c (diff)
downloadgitlab-ce-42572f63eab5db8dc39279e0deeeadef86180a71.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration/openid_connect_provider.md')
-rw-r--r--doc/integration/openid_connect_provider.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/integration/openid_connect_provider.md b/doc/integration/openid_connect_provider.md
index 89f4924d717..f75630b93a2 100644
--- a/doc/integration/openid_connect_provider.md
+++ b/doc/integration/openid_connect_provider.md
@@ -13,7 +13,7 @@ REST-like manner. OIDC performs many of the same tasks as OpenID 2.0,
but does so in a way that is API-friendly, and usable by native and
mobile applications.
-On the client side, you can use [omniauth-openid-connect] for Rails
+On the client side, you can use [OmniAuth::OpenIDConnect](https://github.com/jjbohn/omniauth-openid-connect/) for Rails
applications, or any of the other available [client implementations](https://openid.net/developers/libraries/#connect).
GitLab's implementation uses the [doorkeeper-openid_connect] gem, refer
@@ -48,4 +48,3 @@ Only the `sub` and `sub_legacy` claims are included in the ID token, all other c
[doorkeeper-openid_connect]: https://github.com/doorkeeper-gem/doorkeeper-openid_connect "Doorkeeper::OpenidConnect website"
[OAuth guide]: oauth_provider.md "GitLab as OAuth2 authentication service provider"
-[omniauth-openid-connect]: https://github.com/jjbohn/omniauth-openid-connect/ "OmniAuth::OpenIDConnect website"