Bug 50645 - udm does not take case settings from ldap schema into account
Summary: udm does not take case settings from ldap schema into account
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UDM - CLI
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-16 20:02 CET by Christian Völker
Modified: 2024-06-27 12:10 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
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.034
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019121221000578
Bug group (optional):
Customer ID: 00009
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-12-16 20:02:18 CET
The ldap schema defines if an attribute is case sensitive or not:

attributetype ( 1.3.6.1.4.1.10176.99999.2.23159  NAME 'testAttribute9'
        DESC 'Free customer attribute'
        EQUALITY caseIgnoreMatch
        SUBSTR caseIgnoreSubstringsMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
 

univention-ldapsearch takes this into account and prints objects with "testAttribute9=Example" as well as "testAttribute=EXAMPLE".

But udm does not consider the case when editing the value.

udm computers/windows modify --dn "$DN" --remove testAttribute9=Example does not remove an attribute with EXAMPLE as value, but ldapsearch find it.


udm should consider ldap schema, too.
Comment 1 Florian Best univentionstaff 2019-12-17 09:42:49 CET
The patch-draft at Bug #43286 has to goal to achieve this.
Comment 2 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:03 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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