Bug 47868 - UDM module windows/domaincontroller has property service (univentionService) but LDAP schema doesn't
UDM module windows/domaincontroller has property service (univentionService) ...
Status: NEW
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-09-26 22:18 CEST by Daniel Tröder
Modified: 2021-05-03 21:50 CEST (History)
1 user (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?: 5: Will affect all 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.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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.
Description Daniel Tröder univentionstaff 2018-09-26 22:18:04 CEST
There is a mapping in windows_domaincontroller.py:361 for service→univentionService, and thus a service drop-down in UMC, but the associated LDAP schema (univention.schema:163) doesn't support the attribute.

When saving a computers/windows_domaincontroller UDM object with one or more services, this leads to:

-----------------------------------------
ldapError: Object class violation: attribute 'univentionService' not allowed
-----------------------------------------

Either the "univentionService" attribute must be added to the objectClass "univentionWindows" or the mapping must be removed.
Backwards compatibility is not an issue, as this has never worked and thus there is no data to protect.