Bug 48032 - settings/office365profile has no identifying property
settings/office365profile has no identifying property
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Office 365
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-10-20 21:20 CEST by Daniel Tröder
Modified: 2021-05-14 16:34 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?: 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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
best: Patch_Available+


Attachments
patch (1.29 KB, patch)
2019-03-30 08:55 CET, Florian Best
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2018-10-20 21:20:04 CEST
No property in modules/univention/handler.d/office365profile.py has identifies=True. The value of 'name' is however used to identify settings/office365profile objects.

property_descriptions = {
	'name': univention.admin.property(
		short_description=_(u'Profile name'),
		long_description=_(u'Displayed profile name when selecting a profile'),
		syntax=univention.admin.syntax.string,
		multivalue=False,
		required=True,
		may_change=True,
		identifies=False
	),

IMHO property_descriptions['name']['identifies] should be True.
Comment 1 Florian Best univentionstaff 2019-03-30 08:55:03 CET
Created attachment 9949 [details]
patch

Yes, use the generic UDM behavior!
Comment 2 Ingo Steuwer univentionstaff 2021-05-14 15:42:27 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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