Skip to content

Conversation

@testeddoughnut
Copy link
Contributor

It seems Debian 12 defaults to socket activation of the sssd responders. This adds the ability to omit the services option in sssd's config.

Example errors when sssd starts without this change:

sssd_check_socket_activated_responders[36889]: [sssd] [main] (0x0070): Misconfiguration found for the sudo responder.
sssd_check_socket_activated_responders[36889]: The sudo responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf.
sssd_check_socket_activated_responders[36889]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the sudo's socket by calling:
sssd_check_socket_activated_responders[36889]: "systemctl disable sssd-sudo.socket"

It seems Debian 12 defaults to socket activation of the sssd responders.
This adds the ability to omit the services option in sssd's config.

Signed-off-by: M. David Bennett <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant