Looks to me like it's because the PAM service "unity" (which runs the screensaver) isn't listed in the `ad_gpo_map_interactive` option in sssd.conf. This list should have distro-specific defaults (since different distributions use different PAM service names)
The fix should be to add unity to the default set (and the manpage), but anyone experiencing this issue right now should be able to add the following to their [domain/DOMAINNAME] section of sssd.conf to work around it:
```
ad_gpo_map_interactive = +unity
```
I suppose this might not be an unreasonable default to add upstream as well, so I just sent a patch there. I'd recommend that the maintainers of this package in Ubuntu and Debian should carefully examine which PAM services are available (including in variants like Kubuntu and Xubuntu) and add them to the defaults downstream.
Looks to me like it's because the PAM service "unity" (which runs the screensaver) isn't listed in the `ad_gpo_ map_interactive ` option in sssd.conf. This list should have distro-specific defaults (since different distributions use different PAM service names)
The fix should be to add unity to the default set (and the manpage), but anyone experiencing this issue right now should be able to add the following to their [domain/DOMAINNAME] section of sssd.conf to work around it:
``` map_interactive = +unity
ad_gpo_
```
I suppose this might not be an unreasonable default to add upstream as well, so I just sent a patch there. I'd recommend that the maintainers of this package in Ubuntu and Debian should carefully examine which PAM services are available (including in variants like Kubuntu and Xubuntu) and add them to the defaults downstream.