Bug 43131 - Missing information in case of an exception (ucsschool lib Attribute)
Missing information in case of an exception (ucsschool lib Attribute)
Status: CLOSED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Import scripts
UCS@school 4.1 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-12-07 14:56 CET by Daniel Tröder
Modified: 2023-06-12 15:39 CEST (History)
2 users (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?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, External feedback, Troubleshooting
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2016-12-07 14:56:05 CET
+++ This bug was initially created as a clone of Bug #42942 +++

If a Users property (ucsschool.lib.Attribute) is of a different type than the value written into it, then when create()/modify() is run, the resulting Exception is not caught, crashing the entire import lib/script.

Depending on the Attribute the excpetions are of type AttributeError, KeyError, TypeError or ValueError and occur in ldap/filter.py, univention/uldap.py or admin/syntax.py.

Reproduce with:
astud = ImportStudent.from_dn("...", None, lo)
astud.birthday = {'a': "A"}  # email, record_uid, lastname
astud.modify(lo)
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:43:48 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with
bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.