Description of problem:
Attempt to clone any repository managed by Business Central over SSH ends like this:
> $ git clone -v ssh://firstname.lastname@example.org:8001/system
> Cloning into 'system'...
> Password authentication
> Invalid credentials.fatal: Could not read from remote repository.
> Please make sure you have the correct access rights
> and the repository exists.
Although server log inidicates successful authentication:
> 12:25:05,201 INFO [org.apache.sshd.server.session.ServerSession] (sshd-SshServer[45ebea8a]-nio2-thread-5) Server session created from /127.0.0.1:58070
> 12:25:05,202 INFO [org.apache.sshd.server.session.ServerSession] (sshd-SshServer[45ebea8a]-nio2-thread-5) Kex: server->client aes128-ctr hmac-md5 none
> 12:25:05,202 INFO [org.apache.sshd.server.session.ServerSession] (sshd-SshServer[45ebea8a]-nio2-thread-5) Kex: client->server aes128-ctr hmac-md5 none
> 12:25:07,132 INFO [org.apache.sshd.server.session.ServerUserAuthService] (sshd-SshServer[45ebea8a]-nio2-thread-4) Session admin@/127.0.0.1:58070 authenticated
> 12:25:07,135 INFO [org.apache.sshd.server.channel.ChannelSession] (sshd-SshServer[45ebea8a]-nio2-thread-5) Executing command: git-upload-pack '/system'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch Business Central deployed on EAP.
2. Run git clone -v ssh://<admin_user>@127.0.0.1:8001/system where admin_user is a user with admin role. (It may be neccessary to remove an old 127.0.0.1 host fingerprint from ~/.ssh/known_hosts and confirm the new fingerprint.)
Authentication phase fails on clinet, cloning does not start.
Repository should be cloned successfully.
Worked in ER2.
Cloning using git:// protocol works (git clone git://127.0.0.1:9418/system).
It works for me, are you sure you have the expected roles?
Yes, I have a user named 'admin' with password 'admin' and role 'admin'.
Java (EAP runtime):
java.vendor = Oracle Corporation
java.version = 1.7.0_71
git version 1.9.3
Any other information you would need? Please move the bug to MODIFIED if you believe it has been fixed, so that we can verify it in the next build. The problem may not manifest in community builds or may depend on certain environment. It exists in the product though and we need to investigate.
Fixed now, I couldn't reproduce before as my admin user on EAP was configured `wrongly` - here the fix:
Fix verified. Users with any of admin, analyst or developer roles are able to clone repositories.