Lukas et al.,
Thank you for the suggestion. I'll test that as soon as convenient. I'm currently attending SC19 so spinning up labs is something best managed in the mornings with coffee :-) .

Curiously I did have to change the ownership of the socket, and a few service, unit files to sssd:root to get them to start. I would like to test the daemon to running as an unprivileged user as much as possible. I did not consider digging into the files themselves to check configured runtime users, I should've.

As to your question I currently have no real use case for the socket based responders other than their potential for system level optimisation in large enterprise deployments and kicking the tyres on the SSSD feature set to both experiment with it and document the assessment, results, and configuration nuances and requirements.

I often share these results in attempts to help others deploying the daemon and advocate for its use. Similar to this community :-) .

Thank you again and I'll test asap and report what I find,

-- lawrence

On Wed, Nov 20, 2019 at 11:16 AM Lukas Slebodnik <> wrote:
On (15/11/19 05:23), Lawrence Kearney wrote:
>SSSD team,
>Just checking in on this post. Any thoughts why the socket based responders
>would be crashing? Is there any additional info I could provide that would
>be useful?
>Thank you as always!

sssd on rhel7 has hardcoded unprivileged user "sssd" for responders.
And mixing privileged sssd and unprivileged users is not a good idea.

sh# rpm -q sssd-common

sh# systemctl cat sssd-pam.service
# /usr/lib/systemd/system/sssd-pam.service
Description=SSSD PAM Service responder

Also=sssd-pam.socket sssd-pam-priv.socket

ExecStartPre=-/bin/chown sssd:sssd /var/log/sssd/sssd_pam.log
ExecStart=/usr/libexec/sssd/sssd_pam ${DEBUG_LOGGER} --socket-activated
    and here

It works well when sssd is running fully in unprivileged mode.
"user = sssd" in "sssd" section of sssd.conf

Other option would be to override service files for responder in

But I would like to ask why do you want to use socket activated responders on

sssd-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives: