Hi Dimitar!
FreeIPA might be worth a look. We already have a user management system
that currently manages passwd/shadow. The idea was to migrate
passwd/shadow info to 389DS so we could distribute the users across
multiple servers. Perhaps our management system could use FreeIPA's
tools for us
Hi Mitja,
>From the description of the problem it seems that the usermod - SSSD
integration is not working. 389DS just stores the user information but SSSD
is not enforcing the policy, and usermod fails because the user info is not
stored locally.
I think you should consider using FreeIPA instead
Hi Dimitar!
We only want to SSSD with 389DS instead of the local passwd/shadow
files. We do not want to go full IPA for this server.
Setting up SSSD with authconfig automatically set up PAM and
/etc/nsswitch.conf.
SSSD will only be used for these (nsswitch.conf):
passwd:files sss
shadow:
Hi MItja,
it looks like you are trying to integrate SSSD with FreeIPA. I think the
following presentation will help you review the SSSD configuration even if
you are trying to use 389DS independently:
http://www.freeipa.org/images/7/77/Freeipa30_SSSD_SUDO_Integration.pdf
Check the page titled " E
Hi!
How to get usermod working with SSSD/389DS ?
We have SSSD set up on our server and it uses 389DS.
SSSD was enabled with the following command:
authconfig --enablesssd --enablesssdauth --ldapbasedn=dc=example,dc=com
--enableshadow --enablemkhomedir --enablelocauthorize --update
Running for
5 matches
Mail list logo