#93 passwordexpirationtime is 1h less than setup
Closed: wontfix None Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=557724

Description of problem:
If you setup a password policy (subtree in my case) with a passwordmaxage = x,
and then change the password of a user, it will have a passwordexpirationtime =
x - 3600.

For example, passwordmaxage setup to 1day from the console would actually
reflect a passwordexpirationtime in 23 hours.

Version-Release number of selected component (if applicable):
Directory server 1.2.2
Console framework 1.1.3

How reproducible:

Steps to Reproduce:
1. Create a subtree password policy
2. Set "Password expires after 1 day"
3. Change the password of a user under this subtree
4. Check this user advanced properties

Actual results:
The passwordexpirationtime will be approximately "now + 23h"

Expected results:
The passwordexpirationtime should be "now + 1day"

Additional info:
Maybe it's a problem in the timezones. I have my timezone setup to
Europe/Paris, which is GMT+1 ... could it be the reason ?

batch update to FUTURE milestone

Added initial screened field value.

Metadata Update from @nkinder:
- Issue set to the milestone: N/A

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/93

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata