GitLab SSH asks for a password and ignores SSH keys

Question

I have a new gitlab-omnibus installation in a CentOS 6 box, I configured it correctly and can access the web interface. I added my SSH key, however, when I try to execute Git Clone a new installation repo, I ask for the password for the Git user via SSH. I tried this with three different machines and three different accounts, and the problem still persists.

Here is the result from detailed SSH

╭─ jacobclark@Jacobs-MacBook-Pro ~ ╰─$ ssh -vT git@gitlab 130 ↵ OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: Connecting to gitlab [37.26.93.221] port 22. debug1: Connection established. debug1: identity file /Users/jacobclark/.ssh/id_rsa type 1 debug1: identity file /Users/jacobclark/.ssh/id_rsa-cert type -1 debug1: identity file /Users/jacobclark/.ssh/id_dsa type -1 debug1: identity file /Users/jacobclark/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA a1:62:aa:51:0c:20:f3:3e:10:17:c7:20:a4:0b:7b:16 debug1: Host 'gitlab.' is known and matches the RSA host key. debug1: Found key in /Users/jacobclark/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/jacobclark/.ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Trying private key: /Users/jacobclark/.ssh/id_dsa debug1: Next authentication method: password git@gitlab password: 

Answer 1

You need to disable selinux: setenforce 0

Answer 2

I had the same problem for CentOs, it turned out that Centrify is used to manage ssh keys, which is non-standard, but part of the corporate server management processes.

I am not too familiar with Centrify, since it is controlled by a different team, but I solved this problem by creating a sim link from the gitlab authorized keys file in / etc / sshd / auth -keys / git.

The given key file value provided me with the location to be accessed using sshd -T

The result of this is the solution to my problem:

 ln -s /var/opt/gitlab/.ssh/authorized_keys /etc/ssh/auth-keys/git