URL:
https://github.com/SSSD/sssd/pull/703
Title: #703: nss: sssd returns '/' for emtpy home directories
simo5 commented:
"""
On Tue, 2018-12-04 at 04:51 -0800, Jakub Hrozek wrote:
Thanks, this passes the test. And of course the patch is correct,
but after some more testing, I wonder if we should at least for one
release default to fallback_homedir=$something at least for the AD
provider. Because now with the completely minimal AD provider
configuration (no POSIX attrs, ID mapping only) I can't log in with
an AD user:
```
$ getent passwd administrator(a)win.trust.test
administrator@win.trust.test:*:215000500:215000513:Administrator::/bi
n/bash
$ su - administrator(a)win.trust.test
su: user administrator(a)win.trust.test does not exist
```
Note that this is minimal config, realmd already adds
fallback_homedir.
Why this fails? Because of the missing homedir ?
Or at least we should IMO add some backwards compatible handling
when
this patch makes it to fedora or RHEL otherwise admins might not be
happy. From purely upstream point of view this change is probably OK
with me.
I think the AD provider should synthetize an home dir by default,
without any specific option being set, it's what is considered normal
also in winbind land, in fact I would look closely at what winbind does
and do the same for AD users by default.
If fallback_homedir is set, skip the default and use what that setting
specifies.
Simo.
--
Simo Sorce
Sr. Principal Software Engineer
Red Hat, Inc
"""
See the full comment at
https://github.com/SSSD/sssd/pull/703#issuecomment-444101678