Hi hackers,
those of you who are using neither .ldap agent nor any yast2-users API may hit
Delete now.
For others, I would like to announce that .ldap agent now uses original LDAP
names of the object keys that are returned as a result of a search. For
example, the search for user object which returned
$[
"uidnumber" : 1000,
"homedirectory" : "/home/hh",
"uid" : "hh"
]
now returns
$[
"uidNumber" : 1000,
"homeDirectory" : "/home/hh",
"uid" : "hh"
]
This change (required by feature 303596) affects the return value of
all .ldap.search calls, so please check your code. I tried to grep for agent
usage and update yast2-mail, yast2-ldap-server and yast2-samba-server, see
the attached diff. Please review, or at least test it and submit the changes.
The change also affects the API of yast2-users, since the module uses for its
internal user and group representation the same keys as are defined for LDAP.
So if you are using the keys directly, e.g. you are changing user name in
this way:
Users::SelectUser (1000);
Users::EditUser ($[ "uidnumber" : 1111 ]);
Users::CommitUser () etc.
you have to change the line where the internal key is used, i.e.
Users::EditUser ($[ "uidNumber" : 1111 ]);
(However, I haven't find anyone using yast2-users module to add or edit users)
If anything is not clear enough, please ask.
Jiri
--
Jiri Suchomel
SUSE LINUX, s.r.o. e-mail: jsuchome(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Praha 9, Czech Republic http://www.suse.cz
