On Fri, Mar 22, 2013 at 04:19:39PM +0100, Jakub Hrozek wrote:
> Then maybe SSSD is tripping over the absence of the SELinux map order.
> At least that's the way I read the SSSD code, it relies on the presence
> of the ipaSELinuxUserMapOrder attribute.
> What does:
> $ ipa config-show --all --raw | grep -i selinux
> say?


[janfrode@ipa1 ~]$ ipa config-show --all --raw | grep -i selinux
[janfrode@ipa1 ~]$

> Does the problem go away if you set:
> selinux_provider = none
> In the config file in the domain section?

I have added this to one of my clients. Will report back if the problem
is gone or happens again.


Freeipa-users mailing list

Reply via email to