Univention Bugzilla – Bug 46262
strange option handling in udm for users/user
Last modified: 2019-02-27 18:05:52 CET
-> udm users/user create --option ldap_pwd --set lastname=test1 \ --set password=univention --set username=ldap_pwdd -> udm users/user create --option foo --set lastname=test1 \ --set password=univention --set username=fooo -> udm users/user create --option pki --set lastname=test1 \ --set password=univention --set username=pki -> udm users/user create --set lastname=test1 --set password=univention \ --set username=defaulta -> /usr/share/univention-directory-manager-tools/univention-migrate-users-to-ucs4.3 --check Ignoring non users/user account: uid=sys-idp-user,cn=users,dc=fb,dc=bf Modifying uid=ldap_pwdd,dc=fb,dc=bf [('objectClass', [], ['organizationalPerson', 'univentionMail', 'inetOrgPerson'])] Modifying uid=fooo,dc=fb,dc=bf [('objectClass', [], ['organizationalPerson', 'univentionMail', 'inetOrgPerson'])] Modifying uid=pki,dc=fb,dc=bf [('objectClass', [], ['organizationalPerson', 'univentionMail', 'inetOrgPerson'])] seems that default option is always applied, but not person, does this make sense? anyhow, in 4.3 all udm users/create commands should create object that are OK for univention-migrate-users-to-ucs4.3
Yes, we should implement --append-option for the "create" action. Otherwise one needs to specify all(!) options which should be enabled. But one doesn't know which options are enabled by default because there might exists extended options.
Fixed as a result of Bug #45842 Comment 57. *** This bug has been marked as a duplicate of bug 45842 ***
OK
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".