Bug 47876 - maxPwdAge is rejected even when the value is in the bounds
maxPwdAge is rejected even when the value is in the bounds
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
https://bepasty.knut.univention.de/uV...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-09-27 13:07 CEST by Nico Stöckigt
Modified: 2021-05-14 16:34 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
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.114
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018072521000467
Bug group (optional):
Max CVSS v3 score:


Attachments
bug47876.patch (515 bytes, patch)
2018-10-01 12:33 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2018-09-27 13:07:56 CEST
When setting 'pwdMaxAge' back to '0' the internal value is '-9223372036854775808'. That value than is synced to UCS/OpenLDAP but the S4 connector rejects the change.

==================================================
27.09.2018 12:20:43,19 LDAP        (ERROR  ): InvalidSyntax: Maximum password age: Value out of bounds (0 - 86313600 seconds) (dc=domain,dc=tld)
==================================================

The issue is reproducible - see my testing environment 10.200.42.10 (master)

My system was: 4.3-2 errata237
Customers System was:  4.3-1
Comment 1 Arvid Requate univentionstaff 2018-10-01 12:33:25 CEST
Created attachment 9686 [details]
bug47876.patch
Comment 2 Ingo Steuwer univentionstaff 2021-05-14 15:42:02 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.