Hello,

I think the problem come from my DC and the GPO part. I can install a windows DC to perform test, would you recommend 2008 or 2012 ?

Thanks by advance.

On Wed, Apr 20, 2016 at 1:39 PM, Sumit Bose <sbose@redhat.com> wrote:
On Wed, Apr 20, 2016 at 12:11:05PM +0200, Rolla Matthieu wrote:
> Hello,
>
> Thank you for your answer. The file gpo_child is empty :
>
> root@gtw-template:/var/log/sssd# ls -ltr
> total 14656
> -rw------- 1 root root        0 Apr 19 21:44 gpo_child.log
> -rw------- 1 root root     3050 Apr 19 23:16 sssd_pam.log
> -rw------- 1 root root     3050 Apr 19 23:16 sssd_nss.log
> -rw------- 1 root root    21970 Apr 19 23:22 sssd.log
> -rw------- 1 root root    49771 Apr 19 23:22 ldap_child.log
> -rw------- 1 root root   112878 Apr 19 23:22 krb5_child.log
> -rw------- 1 root root 14800060 Apr 20 00:33 sssd_hq.mydc.com.log
>
> Do you want me to attach an other one ?

No, I just realized that the error happens even before the child is
called. It looks like some unexpected data is received.

I wonder if you can try to following using gdb after installing the sssd
debuginfo file?

    gdb -p $(pidof sssd_be)
    (gdb) break ad_gpo_parse_machine_ext_names
    (gdb) continue

try to authenticate while keeping gdb running, whenever gdb show the
prompt again please type

    (gdb) bt full
    (gdb) continue

until the authentication finally fails. Please send me the gdb output.

If this won't work for you I can try to prepare an instrumented build
for you which writes the needed data into the logs. For this I need to
know the exact version of the SSSD package you are using.

bye,
Sumit

>
> Thank you by advance.

> _______________________________________________
> sssd-users mailing list
> sssd-users@lists.fedorahosted.org
> https://lists.fedorahosted.org/admin/lists/sssd-users@lists.fedorahosted.org
_______________________________________________
sssd-users mailing list
sssd-users@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/sssd-users@lists.fedorahosted.org