Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.0 on 2022-01-18 at 14:00 UTC+1 (a few minutes of down time)

Commit b640a9ca authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Bitbucket import: changing the OAuth provider name

All Bitbucket imports now use a specific OAuth provider,
`bitbucket_import`, solving #156.

Simple SSO operations (sign-up/sign-in) are not affected:
they still work with the `bitbucket` provider.
Users will probably want to exclude `bitbucket_import`
from SSO options on the sign-in page (can be done in
the application settings page).

--HG--
branch : heptapod
parent 891d2150cbdd
......@@ -73,7 +73,7 @@ def client
end
def provider
Gitlab::Auth::OAuth::Provider.config_for('bitbucket')
Gitlab::Auth::OAuth::Provider.config_for('bitbucket_import')
end
def options
......
......@@ -59,7 +59,7 @@ def root_url
end
def provider
Gitlab::Auth::OAuth::Provider.config_for('bitbucket')
Gitlab::Auth::OAuth::Provider.config_for('bitbucket_import')
end
def options
......
......@@ -106,7 +106,7 @@ def omniauth_customized_providers
# We override this in EE
def build_omniauth_customized_providers
%i[bitbucket jwt]
%i[bitbucket bitbucket_import jwt]
end
def setup_provider(provider)
......
......@@ -43,5 +43,8 @@ def callback_url
options[:redirect_uri] || (full_host + script_name + callback_path)
end
end
class BitbucketImport < Bitbucket
option :name, 'bitbucket_import'
end
end
end
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment