#1419 sssd incorrectly sets shadowLastChange in seconds not days
Closed: Fixed None Opened 10 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=840089 (Red Hat Enterprise Linux 6)

Description of problem:

The new feature added in 6.3 to set shadowLastChange incorrectly sets the value
in seconds since epoch not days since epoch.

Version-Release number of selected component (if applicable):


Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
owner: somebody => jzeleny
tests: => 0
testsupdated: => 0
upgrade: => 0

master: 33988e4

milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 5
patch: 0 => 1
resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to jzeleny
- Issue set to the milestone: SSSD 1.9.0 beta 5

5 years ago

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2461

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.

Login to comment on this ticket.