Bug 49591 - Traceback in sync from ucs after upgrade to 4.4 - SysErr problem 22
Traceback in sync from ucs after upgrade to 4.4 - SysErr problem 22
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Arvid Requate
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-06-04 10:22 CEST by Christian Völker
Modified: 2019-06-05 11:20 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.023
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019042421000374
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 2 Arvid Requate univentionstaff 2019-06-04 15:48:16 CEST
Reproducable with that addlist against Windows AD Server 2008R2:

root@master10:~# ldbadd -H ldap://10.200.8.126 -UAdministrator%Univention.2 <<%EOF
dn: cn=foo_someusername_test,cn=users,DC=w2k8r2d2ar,DC=net
objectClass: top
objectClass: user
objectClass: person
objectClass: organizationalPerson
sAMAccountName: foo_someusername_test
%EOF
ERR: Other : "LDAP error 80 LDAP_OTHER -  <00000523: SysErr: DSID-031A123E, problem 22 (Invalid argument), data 0> <>" on DN cn=foo_someusername_test,cn=users,DC=w2k8r2d2ar,DC=net at block before line 6
Add failed after processing 0 records


root@master10:~# echo -n foo_someusername_test | wc -c
21

user name too long. In my test the AD-Server accepted up to 20 chars.
Comment 3 Christian Völker univentionstaff 2019-06-05 11:20:26 CEST
Instead of a traceback we should show a proper readable error message.