Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5485

Closed
Open
Created Oct 30, 2013 by Administrator@rootOwner

GitLab 6.2 Access Denied for me, but others work correctly.

Created by: animedbz16

I am not sure what the issue is, but here is the problem I am experiencing.

I have setup GitLab with LDAP support. I logged in and GitLab created my user from LDAP. Another person logs in via LDAP to create their account.

We both create a test repo in our own user names spaces and have given access to the other.

I am unable to push/pull from my own repo as well as the other person's repo.

However, the other person is able to push changes into his repo as well as mine.

I consistently get the Access Denied message.

I had been testing with a 4096 RSA ssh key, while the other person was using a default 2048 key. I had him create me a key off his machine since his machine and 2048 key was working. We add the key to my user via the GitLab UI and attempt to pull, but receive the Access Denied message.

I don't think there is any issue with how gitlab-shell is configured since he is able to push/pull the repositories.

The gitlab-shell.log files shows: https://gist.github.com/animedbz16/7235157

In looking at these logs, I noticed a minor issue listed separately: https://github.com/gitlabhq/gitlabhq/issues/5486

ssh -T [email protected] returns the proper response for both of us: Red Hat Enterprise Linux Server release 6.3 (Santiago) Kernel 2.6.32-279.el6.x86_64 on an x86_64

Welcome to GitLab, Last, First!

GitLab ENV: [git@server gitlab]$ bundle exec rake gitlab:env:info RAILS_ENV=production

System information System: RedHatEnterpriseServer 6.3 Current User: git Using RVM: yes RVM Version: 1.23.12 Ruby Version: 2.0.0p247 Gem Version: 2.1.10 Bundler Version:1.3.5 Rake Version: 10.1.0

GitLab information Version: 6.2.1 Revision: f2a77a82 Directory: /export/appl/pkgs/gitlab/gitlab DB Adapter: mysql2 URL: https://gitlab.domain.com HTTP Clone URL: https://gitlab.domain.com/some-project.git SSH Clone URL: [email protected]:some-project.git Using LDAP: yes Using Omniauth: no

GitLab Shell Version: 1.7.1 Repositories: /export/appl/pkgs/gitlab/repositories/ Hooks: /export/appl/pkgs/gitlab/gitlab-shell/hooks/ Git: /home/git/bin/git

[git@server gitlab]$ bundle exec rake gitlab:check RAILS_ENV=production Checking Environment ...

Git configured for git user? ... yes Has python2? ... yes python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.1 ? ... OK (1.7.1) Repo base directory exists? ... yes Repo base directory is a symlink? ... no Repo base owned by git:git? ... yes Repo base access is drwxrws---? ... yes update hook up-to-date? ... yes update hooks in repos are links: ... Last, First / TestA ... ok Last1, First1 / mytest ... ok Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Check directories and files: /export/appl/pkgs/gitlab/repositories: OK /export/appl/pkgs/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Sidekiq ...

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

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes Database is SQLite ... no All migrations up? ... yes GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Init script exists? ... yes Init script up-to-date? ... yes projects have namespace: ... Last1, First1 / TestA ... yes Last, First / mytest ... yes Projects have satellites? ... Last1, First1 / TestA ... yes Last, First / mytest ... yes Redis version >= 2.0.0? ... yes Your git bin path is "/home/git/bin/git" Git version >= 1.7.10 ? ... yes (1.8.4)

Checking GitLab ... Finished

I am thinking there must be something specific with my user that is created via LDAP or something else specific to my user that is causing the Access Denied message.

Any thoughts?

Assignee
Assign to
Time tracking