Bug 47366 - always set univentionObjectType
Summary: always set univentionObjectType
Status: CLOSED DUPLICATE of bug 47844
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
Version: UCS 4.3
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Daniel Tröder
QA Contact: Dirk Wiesenthal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-17 15:53 CEST by Jannik Ahlers
Modified: 2025-12-10 11:58 CET (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jannik Ahlers univentionstaff 2018-07-17 15:53:09 CEST 
Currently we cannot rely on univentionObjectType, for example if an LDAP object was created externally. Back then it was only implemented for performance improvements. The wish is that we can rely on the attribute, e.g. for search filters.

The idea is that there is a diagnostic module that finds the objects and adds the univentionObjectType with a button 'Fix Problem'.
Comment 1 Daniel Tröder univentionstaff 2018-08-13 13:42:50 CEST 
(Btw: A listener module could do this "live".)

The question is mainly what the criteria are, for an LDAP object to be considered of a certain univentionObjectType.
Comment 2 Florian Best univentionstaff 2019-02-07 17:24:52 CET 
I don't think we should change this. Why do you want to rely on univentionObjectType. This is currently forbidden. If you want to identify an object then you have to use the filter defined by that object type. I think UDM should work without the univentionObjectType attribute. Maybe one day we even can get rid of it completely.
Comment 3 Daniel Tröder univentionstaff 2019-02-11 12:47:06 CET 

*** This bug has been marked as a duplicate of bug 47844 ***
Comment 4 Dirk Wiesenthal univentionstaff 2019-02-11 12:58:55 CET 
Yes duplicate.

(In reply to Florian Best from comment #2)
> I don't think we should change this. Why do you want to rely on
> univentionObjectType.

This is not for UDM, but rather for 3rd parties that want a convenient and reliable LDAP filter.
Comment 5 Daniel Tröder univentionstaff 2019-02-11 13:12:20 CET 
It's also *much* faster than complex filters, like the one for users/user.
Comment 6 Florian Best univentionstaff 2025-12-10 11:55:16 CET 
(In reply to Stefan Gohmann from Bug #38075 comment #2)
> univentionObjectType is only for performance optimization.

This is the reason for my opinion back then:

(In reply to Florian Best from comment #2)
> I don't think we should change this. Why do you want to rely on
> univentionObjectType. This is currently forbidden. If you want to identify
> an object then you have to use the filter defined by that object type. I
> think UDM should work without the univentionObjectType attribute. Maybe one
> day we even can get rid of it completely.

But I think the situation changed. We should make univentionObjectType a MUST attribute in the schema.
There are still so many systems not having it set. But new developers tend to think they can just use it.
The diagnostic module from Bug #47844 helps, but doesn't find all entries.
The only object where it's ensured to have it is users/user.