yast2 ldap-server and yast2 user/group management

[pjaouen]

Hello,
I am struggling with ldap 389-ds since suse 42.x
something is correctly running now with 389-ds-1.4.4.1~git0.2333d75d5-lp151.95.1.x86_64 and yast2-auth-server-4.2.3-lp151.70.1.noarch but yast2 users/groups management (ldap filter) does not work correctly with them

I can get the demo_user with dsidm :
ceres:~ # cat .dsrc
[ceres-y]
uri = ldap://ceres.2sapins.ponctey.fr
basedn = dc=2sapins,dc=ponctey,dc=fr
binddn = cn=Directory Manager

ceres:~ # dsidm ceres-y account list
Enter password for cn=Directory Manager on ldap://ceres.2sapins.ponctey.fr:
dc=2sapins,dc=ponctey,dc=fr
ou=groups,dc=2sapins,dc=ponctey,dc=fr
ou=people,dc=2sapins,dc=ponctey,dc=fr
ou=permissions,dc=2sapins,dc=ponctey,dc=fr
ou=services,dc=2sapins,dc=ponctey,dc=fr
uid=demo_user,ou=people,dc=2sapins,dc=ponctey,dc=fr
cn=demo_group,ou=groups,dc=2sapins,dc=ponctey,dc=fr

with yast2-users with LDAP filter and anonymous login I can see the demo user but not with the right password in order to enter modifications :
La connexion au serveur LDAP n'a pas pu être établie.
Invalid credentials
(No such entry)

NB the demo-user has ID 99998 instead of 1000<ID<60000

[ancorgs]

Since the yast2-auth-server package is developed and maintained by the Samba Team at SUSE, instead of the core YaST Team, I'm adding the "other-maintainer" label to this in order to help filtering the various list of issues.