From 42572f63eab5db8dc39279e0deeeadef86180a71 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Mon, 30 Sep 2019 06:06:02 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/integration/openid_connect_provider.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc/integration/openid_connect_provider.md') 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" -- cgit v1.2.1