Bug 47403 - inconsistent behavior of UDM Python property pwdChangeNextLogin
inconsistent behavior of UDM Python property pwdChangeNextLogin
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-07-26 15:09 CEST by Daniel Tröder
Modified: 2020-06-22 18:53 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?: 2: Will only affect a 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.069
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-07-26 15:09:36 CEST
When the "user must change password next login" option is set, the Python-UDM property "pwdChangeNextLogin" is set to the string '1'.

When it is not set, the value is '' (empty string).

To disable the option, pwdChangeNextLogin must be set to the string '0'.
(Setting it to '' or None will not result in an error, but will be silently ignored.)

After setting the property to '0', running modify() and reloading the UDM object, the value is not '0' anymore, but is now '' (empty string).

1. The property should be represented as a boolean.
2. When modified, it should keep the value, and not change it to a different one.