1. Follow the [Initial OmniAuth Configuration](omniauth.md#initial-omniauth-configuration)
for initial settings.
1. Add the Bitbucket provider configuration:
1. Add the Bitbucket provider configuration:
For Omnibus packages:
For Omnibus packages:
```ruby
```ruby
gitlab_rails['omniauth_enabled'] = true
gitlab_rails['omniauth_providers'] = [
gitlab_rails['omniauth_providers'] = [
{
{
"name" => "bitbucket",
"name" => "bitbucket",
...
@@ -96,10 +99,13 @@ you to use.
...
@@ -96,10 +99,13 @@ you to use.
For installations from source:
For installations from source:
```yaml
```yaml
- { name: 'bitbucket',
omniauth:
app_id: 'BITBUCKET_APP_KEY',
enabled: true
app_secret: 'BITBUCKET_APP_SECRET',
providers:
url: 'https://bitbucket.org/' }
- { name: 'bitbucket',
app_id: 'BITBUCKET_APP_KEY',
app_secret: 'BITBUCKET_APP_SECRET',
url: 'https://bitbucket.org/' }
```
```
---
---
...
@@ -121,6 +127,9 @@ well, the user will be returned to GitLab and will be signed in.
...
@@ -121,6 +127,9 @@ well, the user will be returned to GitLab and will be signed in.
Once the above configuration is set up, you can use Bitbucket to sign into
Once the above configuration is set up, you can use Bitbucket to sign into
GitLab and [start importing your projects][bb-import].
GitLab and [start importing your projects][bb-import].
If you don't want to enable signing in with Bitbucket but just want to import
projects from Bitbucket, you could [disable it in the admin panel](omniauth.md#enable-or-disable-sign-in-with-an-omniauth-provider-without-disabling-import-sources).