#2174 [RFE] Store the "last password change" field with higher resolution than 24 hours
Closed: cloned-to-github 3 years ago by pbrezina. Opened 10 years ago by dpal.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1033252

(Not at all certain what component to file this against; guessing sssd is close
enough to start the discussion, but ultimately this will need to be a part of
the larger user account read/write API initiative.)

sp_lstchg is stored in "days since Jan 1 1970 0:0:0 UTC", which is far too
imprecise - it's not even possible to reliably tell users whether the last
change has happened "today" or "yesterday" when the UTC midnight happens during
their (working) day.

A future system for storing the data, and APIs for accessing it, should have a
higher resolution.  Something that specifies the time to the nearest second
seems like a possible starting proposal.

Fields changed

mark: => 0

Required for local account integration.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
review: True => 0
selected: =>
testsupdated: => 0

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

Required for the local users support

milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0

Metadata Update from @dpal:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: bugzilla

4 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/3216

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 @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata