I have successfully setup sssd that the project members can login with their LDAP credentials.
we also have gitlab installed in the same server, gitlab relies on the SSH trigger (command="..." in authorized_keys file) for git ssh auth.
but the problem is I can't get git ssh auth login success because the gitlab-shell comamnd not triggered:
command="date >> a.log;
/opt/git/gitlab-shell/bin/gitlab-shell key-2",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAsIDug9GByMA0KWakMxt2jJTKhR4Rr53zA3iIGNyI5FFszppaAaKLyEjwi46IcPD6247eiudhNkptqAk5Ao71+iydbkuT882F+IEzgD6f4nl2fBqWyZPN/AtG8ojnQJWVOwN2W02IPgXYx+Kpbg9LAk2ac8nW/JK9A90X8+BmCcdWJzjXzoXp2RsOPeofcXcAyjr5vhHP4ES1xxC+jZ4UcpCbOLhIC1EwHGZk1Kwc1WV7IeZBd0tjjuJs1q9zDzAKNFG93U9cVZ6/92N46TNgHRcp+BRuYpGO/vK1sn2Or3x/hq/ruvjGpes+kFQ35VwSAA2DncPV0CPfn9opUXkcXw== email@example.com
i added "date >> a.log" in front of the gitlab-shell, the expect result is ~/a.log should be generated and datetime are logged in the file.
(i test this on a normal server, which means without SSSD setup, it worked as expected)
but on the SSSD enabled server, i did not see ~/a.log created, that means the command not triggered.
so do you have any clue why the command not triggered?
let me know if need to provide more info, like conf file, etc.
Thanks & Best Regards!
| Nick Tan |