ah, thank you for the explanation. Please try to add to following
modification to the cache of sssd:
cat << EOF_EOF | ldbmodify -H /var/lib/sss/db/cache_YOUR_DOMAIN.ldb
dn: @ATTRIBUTES
changetype: modify
add: originalDN
originalDN: CASE_INSENSITIVE
EOF_EOF
This should make all originalDN comparisons case-insensitive. Please
tell me if this fixes your issue. If yes, I will discuss with the other
sssd developers if it makes sense to include this change to the default
installation.
bye,
Sumit
>
>
> > How was the 'migration' done. Did you export the data on the old server
> > and load them into the new one? Did you remove the sssd cache at some
> > point during the migration?
>
> It's still in progress as we had found this issue. But the migration
> proccess is not so difficult, as we are using FDS for windows AD sync,
> so it's the main storage of information and migration is to add in new
> FDS winsync agreement. Also I'm exploring, maybe, another issue to
> find out where is the problem. So until I solve this issues we will
> not migrate from FDS 1.2.3.
>
> >
> >>
> >> You will find a patch to fix this on sssd side in attach.
> >
> > bye,
> > Sumit
> > _______________________________________________
> > sssd-devel mailing list
> > sssd-devel(a)lists.fedorahosted.org
> >
https://fedorahosted.org/mailman/listinfo/sssd-devel
> >
> _______________________________________________
> sssd-devel mailing list
> sssd-devel(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/sssd-devel
_______________________________________________
sssd-devel mailing list
sssd-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/sssd-devel