It is unclear whether it is an SSSD or server side effort. At least investigation should be conducted by the SSSD team.
Fields changed
milestone: NEEDS_TRIAGE => SSSD Deferred owner: somebody => sbose
rhbz: => 0
Since this ticket is over 6 years old and nobody ever requested this feature, I suggest we just close it.
blockedby: => blocking: => changelog: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: => 0 patch: => 0 review: => 1 selected: => sensitive: => 0
+1
resolution: => invalid status: new => closed
Metadata Update from @dpal: - Issue assigned to sbose - Issue set to the milestone: SSSD Patches welcome
For future Internet archaeologists, I was able to set up gitolite successfully with SSSD by creating a wrapper script for sss_ssh_authorizedkeys, call it /usr/bin/sss_ssh_authorizedkeys_wrapper:
/usr/bin/sss_ssh_authorizedkeys_wrapper
#!/bin/sh sss_ssh_authorizedkeys $@ | while read -r KEY ; do echo "command=\"/usr/share/gitolite3/gitolite-shell $1\",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty $KEY" done
And then changing my sshd_config file accordingly:
AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys_wrapper AuthorizedKeysCommandUser nobody
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1795
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.