Bug 47846 - univentionObjectType not set for kerberos/kdcentry objects
Summary: univentionObjectType not set for kerberos/kdcentry objects
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL:
Keywords:
Depends on: 47844
Blocks:
  Show dependency tree / graph
 
Reported: 2018-09-21 13:10 CEST by Dirk Wiesenthal
Modified: 2025-12-10 11:52 CET (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?: 5: Will affect all installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.057
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 Dirk Wiesenthal univentionstaff 2018-09-21 13:10:09 CEST 
This leads to one-time warnings in customer environments and one of our test fails.

+++ This bug was initially created as a clone of Bug #47844 +++

We should add a diagnostic plugin that scans through all LDAP objects and identifies those that lack "univentionObjectType" but seem to be some sort of  "univention object".

Also we should provide a one-click solution to add these object types.
Comment 1 Florian Best univentionstaff 2025-12-10 11:52:20 CET 
(In reply to Stefan Gohmann from Bug #38075 comment #2)
> univentionObjectType is only for performance optimization. We have to modify
> the Kerberos server because theses objects are directly created via Heimdal.