Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Jérome Perrin
gitlab-ce
Commits
6d756b2b
Commit
6d756b2b
authored
Feb 10, 2017
by
Joe Marty
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix spelling errors in docs and changelog
parent
70f75ca1
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
7 deletions
+7
-7
changelogs/unreleased/26744-add-omniauth-oauth2-generic-strategy.yml
...unreleased/26744-add-omniauth-oauth2-generic-strategy.yml
+1
-1
doc/integration/oauth2_generic.md
doc/integration/oauth2_generic.md
+6
-6
No files found.
changelogs/unreleased/26744-add-omniauth-oauth2-generic-strategy.yml
View file @
6d756b2b
title
:
Add the o
mniaut-oauth2-
generic OmniAuth strategy
title
:
Add the o
auth2_
generic OmniAuth strategy
merge_request
:
9048
author
:
Joe Marty
\ No newline at end of file
doc/integration/oauth2_generic.md
View file @
6d756b2b
# Sign into Git
l
ab with (almost) any OAuth2 provider
# Sign into Git
L
ab with (almost) any OAuth2 provider
The
`omniauth-oauth2-generic`
gem allows Single Sign On between Git
l
ab and your own OAuth2 provider
The
`omniauth-oauth2-generic`
gem allows Single Sign On between Git
L
ab and your own OAuth2 provider
(or any OAuth2 provider compatible with this gem)
This strategy is designed to allow configuration of the simple OmniAuth SSO process outlined below:
1.
Strategy directs client to your authorization URL (
**configurable**
), with specified ID and key
1.
OAuth provider handles authentication of request, user, and (optionally) authorization to access user's profile
1.
OAuth provider directs client back to Git
l
ab where Strategy handles retrieval of access token
1.
OAuth provider directs client back to Git
L
ab where Strategy handles retrieval of access token
1.
Strategy requests user information from a
**configurable**
"user profile" URL (using the access token)
1.
Strategy parses user information from the response, using a
**configurable**
format
1.
Git
l
ab finds or creates the returned user and logs them in
1.
Git
L
ab finds or creates the returned user and logs them in
### Limitations of this Strategy:
-
It can only be used for Single Sign on, and will not provide any other access granted by any OAuth provider
(importing projects or users, etc)
-
It only supports the Authorization Grant flow (most common for client-server applications, like Git
l
ab)
-
It only supports the Authorization Grant flow (most common for client-server applications, like Git
L
ab)
-
It is not able to fetch user information from more than one URL
-
It has not been tested with user information formats other than JSON
...
...
@@ -35,7 +35,7 @@ This strategy is designed to allow configuration of the simple OmniAuth SSO proc
1.
On your GitLab server, open the configuration file.
For
o
mnibus package:
For
O
mnibus package:
```
sh
sudo
editor /etc/gitlab/gitlab.rb
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment