Remove from providers with icon
Remove puts Remove puts
This commit is contained in:
parent
5290c5c32b
commit
a4cf01f32e
10 changed files with 95 additions and 1 deletions
1
Gemfile
1
Gemfile
|
@ -43,6 +43,7 @@ gem 'omniauth_crowd', '~> 2.2.0'
|
|||
gem 'omniauth-authentiq', '~> 0.3.3'
|
||||
gem 'omniauth_openid_connect', '~> 0.3.0'
|
||||
gem "omniauth-ultraauth", '~> 0.0.2'
|
||||
gem 'omniauth-salesforce', '~> 1.0.5'
|
||||
gem 'rack-oauth2', '~> 1.9.3'
|
||||
gem 'jwt', '~> 2.1.0'
|
||||
|
||||
|
|
|
@ -553,6 +553,9 @@ GEM
|
|||
omniauth (~> 1.9)
|
||||
omniauth-oauth2-generic (0.2.2)
|
||||
omniauth-oauth2 (~> 1.0)
|
||||
omniauth-salesforce (1.0.5)
|
||||
omniauth (~> 1.0)
|
||||
omniauth-oauth2 (~> 1.0)
|
||||
omniauth-saml (1.10.0)
|
||||
omniauth (~> 1.3, >= 1.3.2)
|
||||
ruby-saml (~> 1.7)
|
||||
|
@ -1127,6 +1130,7 @@ DEPENDENCIES
|
|||
omniauth-google-oauth2 (~> 0.6.0)
|
||||
omniauth-kerberos (~> 0.3.0)
|
||||
omniauth-oauth2-generic (~> 0.2.2)
|
||||
omniauth-salesforce (~> 1.0.5)
|
||||
omniauth-saml (~> 1.10)
|
||||
omniauth-shibboleth (~> 1.3.0)
|
||||
omniauth-twitter (~> 1.4)
|
||||
|
|
5
changelogs/unreleased/57077-add-salesforce-omniauth.yml
Normal file
5
changelogs/unreleased/57077-add-salesforce-omniauth.yml
Normal file
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
title: Resolve Salesforce.com omniauth support
|
||||
merge_request: 27834
|
||||
author:
|
||||
type: added
|
|
@ -940,6 +940,10 @@ test:
|
|||
app_id: 'YOUR_CLIENT_ID',
|
||||
app_secret: 'YOUR_CLIENT_SECRET',
|
||||
args: { scope: 'aq:name email~rs address aq:push' } }
|
||||
- { name: 'salesforce',
|
||||
app_id: 'YOUR_CLIENT_ID',
|
||||
app_secret: 'YOUR_CLIENT_SECRET'
|
||||
}
|
||||
ldap:
|
||||
enabled: false
|
||||
servers:
|
||||
|
|
BIN
doc/integration/img/salesforce_app_details.png
Normal file
BIN
doc/integration/img/salesforce_app_details.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 113 KiB |
BIN
doc/integration/img/salesforce_app_secret_details.png
Normal file
BIN
doc/integration/img/salesforce_app_secret_details.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 195 KiB |
BIN
doc/integration/img/salesforce_oauth_app_details.png
Normal file
BIN
doc/integration/img/salesforce_oauth_app_details.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 168 KiB |
|
@ -35,6 +35,7 @@ contains some settings that are common for all providers.
|
|||
- [JWT](../administration/auth/jwt.md)
|
||||
- [OpenID Connect](../administration/auth/oidc.md)
|
||||
- [UltraAuth](ultra_auth.md)
|
||||
- [SalesForce](salesforce.md)
|
||||
|
||||
## Initial OmniAuth Configuration
|
||||
|
||||
|
|
79
doc/integration/salesforce.md
Normal file
79
doc/integration/salesforce.md
Normal file
|
@ -0,0 +1,79 @@
|
|||
# SalesForce OmniAuth Provider
|
||||
|
||||
You can integrate your GitLab instance with [SalesForce](https://www.salesforce.com/) to enable users to login to your GitLab instance with their SalesForce account.
|
||||
|
||||
## Create SalesForce Application
|
||||
|
||||
To enable SalesForce OmniAuth provider, you must use SalesForce's credentials for your GitLab instance.
|
||||
To get the credentials (a pair of Client ID and Client Secret), you must register an application on UltraAuth.
|
||||
|
||||
1. Sign in to [SalesForce](https://www.salesforce.com/).
|
||||
|
||||
1. Navigate to **Platform Tools/Apps** and click on **New Connected App**.
|
||||
|
||||
1. Fill in the application details into the following fields:
|
||||
- **Connected App Name** and **API Name**: Set to any value but consider something like `<Organization>'s GitLab`, `<Your Name>'s GitLab`, or something else that is descriptive.
|
||||
- **Description**: Description for the application.
|
||||
|
||||
![SalesForce App Details](img/salesforce_app_details.png)
|
||||
1. Select **API (Enable OAuth Settings)** and click on **Enable OAuth Settings**.
|
||||
1. Fill in the application details into the following fields:
|
||||
- **Callback URL**: The call callback URL. For example, `https://gitlab.example.com/users/auth/salesforce/callback`.
|
||||
- **Selected OAuth Scopes**: Move **Access your basic information (id, profile, email, address, phone)** and **Allow access to your unique identifier (openid)** to the right column.
|
||||
|
||||
![SalesForce Oauth App Details](img/salesforce_oauth_app_details.png)
|
||||
1. Click **Save**.
|
||||
|
||||
1. On your GitLab server, open the configuration file.
|
||||
|
||||
For omnibus package:
|
||||
|
||||
```sh
|
||||
sudo editor /etc/gitlab/gitlab.rb
|
||||
```
|
||||
|
||||
For installations from source:
|
||||
|
||||
```sh
|
||||
cd /home/git/gitlab
|
||||
sudo -u git -H editor config/gitlab.yml
|
||||
```
|
||||
|
||||
1. See [Initial OmniAuth Configuration](omniauth.md#initial-omniauth-configuration) for initial settings.
|
||||
|
||||
1. Add the provider configuration:
|
||||
|
||||
For omnibus package:
|
||||
|
||||
```ruby
|
||||
gitlab_rails['omniauth_providers'] = [
|
||||
{
|
||||
"name" => "salesforce",
|
||||
"app_id" => "SALESFORCE_CLIENT_ID",
|
||||
"app_secret" => "SALESFORCE_CLIENT_SECRET"
|
||||
}
|
||||
]
|
||||
```
|
||||
|
||||
For installation from source:
|
||||
|
||||
```
|
||||
- { name: 'salesforce',
|
||||
app_id: 'SALESFORCE_CLIENT_ID',
|
||||
app_secret: 'SALESFORCE_CLIENT_SECRET'
|
||||
}
|
||||
```
|
||||
1. Change `SALESFORCE_CLIENT_ID` to the Consumer Key from the SalesForce connected application page.
|
||||
1. Change `SALESFORCE_CLIENT_SECRET` to the Client Secret from the SalesForce connected application page.
|
||||
![SalesForce App Secret Details](img/salesforce_app_secret_details.png)
|
||||
|
||||
1. Save the configuration file.
|
||||
1. [Reconfigure GitLab]( ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure ) or [restart GitLab]( ../administration/restart_gitlab.md#installations-from-source ) for the changes to take effect if you
|
||||
installed GitLab via Omnibus or from source respectively.
|
||||
|
||||
On the sign in page, there should now be a SalesForce icon below the regular sign in form.
|
||||
Click the icon to begin the authentication process. SalesForce 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.
|
||||
|
||||
NOTE: **Note:**
|
||||
GitLab requires the email address of each new user. Once the user is logged in using SalesForce, GitLab will redirect the user to the profile page where they will have to provide the email and verify the email.
|
|
@ -14,7 +14,7 @@ describe 'OAuth Login', :js, :allow_forgery_protection do
|
|||
end
|
||||
|
||||
providers = [:github, :twitter, :bitbucket, :gitlab, :google_oauth2,
|
||||
:facebook, :cas3, :auth0, :authentiq]
|
||||
:facebook, :cas3, :auth0, :authentiq, :salesforce]
|
||||
|
||||
before(:all) do
|
||||
# The OmniAuth `full_host` parameter doesn't get set correctly (it gets set to something like `http://localhost`
|
||||
|
|
Loading…
Reference in a new issue