Bug 42170 – Empty string in UCR variables instead of being unset

Bug 42170 - Empty string in UCR variables instead of being unset


Summary:	Empty string in UCR variables instead of being unset

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Univention Configuration Registry
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-29 15:40 CEST by Christina Scheinig
Modified:	2019-01-03 07:20 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	3: Will affect average number of 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.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
traceback caused by the ucrv (6.54 KB, text/x-log) 2016-08-29 15:40 CEST, Christina Scheinig	Details
View All 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 Christina Scheinig

2016-08-29 15:40:09 CEST

Created attachment 7940 [details]
traceback caused by the ucrv

A customer set the UCR variable "ucsschool/userlogon/umclink/filter" to an empty string by mistake. He just wanted to read the variable description and clicked on the list entry. Instead of cancelling the edit mode, he exited the popup dialog via save. In this case, the variable value was set to an empty string which caused the ucsschool-user-logonscripts to fail with a "PROTOCOL_ERROR: {'desc': 'Protocol error'}" (see attached traceback).

It was entirely unclear to the customer that he had set a UCR variable.

A possible solution could be an additional check for empty values with a dialog box.

This happened at Ticket#2016082821000123

Comment 1 Stefan Gohmann

2019-01-03 07:20:45 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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