Bug 16508 - "Enable password expiration" requires "Days before changes allowed" to be non 0
Summary: "Enable password expiration" requires "Days before changes allowed" to be non 0
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-31 04:58 CEST by Henri de Solages
Modified: 2018-10-06 12:59 CEST (History)
1 user (show)

See Also:
Source RPM: userdrake-2.10-1.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Henri de Solages 2015-07-31 04:58:21 CEST 
Description of problem:
When editing "Password info", it is impossible to enable password expiration without setting at least 1 day before changes be allowed.

Version-Release number of selected component (if applicable):
1.13.3 according to "Help"â"About", "2.10.1" according to rpm -qif /usr/bin/drakuser

How reproducible:
Always

Steps to Reproduce:
1. Open Mageia control center â System â Manage users on system â Users
2. Select a user other than yourself.
3. Click on "Edit selected row" â "Password info"
4. Check "Enable password expiration"
5. Fill the field "Days before changes required" with "365".
6. Click on "OK"

Result: the message "Please fill up all field in password aging".

Expected result: the expiration delay should be recorded, without "Days before changes allowed" being changed to something other than 0 if I want do allow more than one change a day.


Reproducible: 

Steps to Reproduce:
David Walser 2015-07-31 16:44:23 CEST

Assignee: bugsquad => thierry.vignaud

Comment 1 Marja Van Waes 2018-04-14 12:04:41 CEST 
Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 2 Marja Van Waes 2018-10-06 12:59:09 CEST 
No reply, so closing as OLD

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.