It happen to me all the time that one of developers notifies me about some kind of problem that I can’t confirm from my account. Sometimes it was because of bad ssh keys configuration, other times file permissions, mostly such stuff. It’s sometimes convenient to “enter into someone’s shoes” to see what’s going on there.
root on machine you may do that like this:
su developer -
Easy one but that’s not enough for all cases. When you use bastion host (or similar solutions) sometimes users have connection problems and it’s harder to check. When such user have
ForwardAgent ssh option enabled you may stole this session to check login problems. After you switch to such user, you may wan’t to hide history (it’s optional 😉 ) - disable history like that:
Now you may stole ssh session, but first check if you have your dev is logged on:
$ ls -la /tmp/ | grep ssh
drwx------ 2 root root 4096 Apr 27 20:56 ssh-crYKv29798
drwx------ 2 developer developer 4096 Apr 27 18:03 ssh-cVXFo28108
SSH_AUTH_SOCK with path to developer’s agent socket:
Finally you may try to login via
ssh as developer and see with his eyes what’s now working.