OAuth integration with GitLab.com

Summary

Gitlab CE does not reflect the integration setup at all

Steps to reproduce

Followed the documentation, added these lines into the /etc/gitlab/gitlab.rb. Gitlab is running on Ubuntu 16.04 AWS EC2 machine.

external_url 'http://***.com'

gitlab_rails['omniauth_providers'] = [
    {
      "name" => "gitlab",
      "app_id" => "***",
      "app_secret" => "***",
      "args" => { "scope" => "api" }
    }
  ]
gitlab_rails['omniauth_enabled'] = true
gitlab_rails['omniauth_allow_single_sign_on'] = ['gitlab']
gitlab_rails['omniauth_block_auto_created_users'] = true

Ran gitlab-ctl restart and event tried to restart whole machine.

Expected behavior

The gitlab icon and auth mechanism should be visible on sign-up page, or some UI to gitlab auth should be visible in Profile Settings/Account as described in the docs.

Actual behavior

Absolutely no change.

Relevant logs and/or screenshots

No relevant logs, updated config is above.

Output of checks

Results of GitLab application Check

$ sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...

GitLab Shell version >= 3.6.6 ? ... OK (3.6.6)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
2/2 ... repository is empty
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Reply by email ...

Reply by email is disabled in config/gitlab.yml

Checking Reply by email ... Finished

Checking LDAP ...

LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab ...

Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ... 
2/2 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.1)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.7.4)
Active users: 1

Checking GitLab ... Finished

Results of GitLab environment info

System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.3.1p112
Gem Version:	2.6.6
Bundler Version:1.13.5
Rake Version:	10.5.0
Sidekiq Version:4.2.1

GitLab information
Version:	8.13.2
Revision:	89a5afc
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		http://ec2-52-211-234-140.eu-west-1.compute.amazonaws.com
HTTP Clone URL:	http://ec2-52-211-234-140.eu-west-1.compute.amazonaws.com/some-group/some-project.git
SSH Clone URL:	git@ec2-52-211-234-140.eu-west-1.compute.amazonaws.com:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	3.6.6
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks/
Git:		/opt/gitlab/embedded/bin/git

Possible fixes

Honestly don't have clue, because I don't know ruby nor gitlab.

Thank you ...

---

Edit: Only reason why I'm asking this is because I need to import a project from actual gitlab.com. The importer says that it won't import the file because of error "bad decrypt" with information If your HTTP repository is not publicly accessible, add authentication information to the URL. But the url is not editable nowhere, after last github update I cannot change the source project visibility to "public" (the UI is gone) and I could not google the solution anywhere. I didn't want to open multiple issues at once .. I'll solve this by pushing the repo manually but I'm still interested where the problem was.

@rudolfdobias Have you recently migrated GitLab to another server?

Added ~532786 label

@markglenfletcher I just installed fresh copy if Gitlab CE on new server. Today I managed to migrate the projects from gitlab.com to my new gitlab instance. The problem was that in documentation are different paths to config that in real.

I found the right config.yml at /opt/gitlab/embedded/service/gitlab-rails/config but the docs are referencing config at /home/git/gitlab/config.

That means the issue is no longer relevant but it would be nice to update the documentation with the correct path IMHO.

Added frontend and removed ~532786 labels

Added ~532786 and removed frontend labels

Hi @rudolfdobias. I think I understand why you are getting the bad decrypt error upon importing your project. If you would still like to transfer your project via an export from GitLab.com and an import to your own instance, please follow the advice in this issue:

Error importing GitLab Project: bad decrypt - https://gitlab.com/gitlab-org/gitlab-ce/issues/24458#note_18620041

Closing this issue down in accordance with our Issue Triage Policies. Please reopen the issue if the you feel that the issue is still relevant. Thanks!

closed