389-ds-base

#51046 Improve passwordHistory processing speed
Closed: wontfix by spichugi. Opened by spichugi.

Closed: wontfix
Reopen Issue

Issue Description

When password policy is enabled and userPassword is set too fast (in a script) few times in a row, only the last password is written to passordHistory attribute.

Package Version and Platform

389-ds-base-1.4.4.0-20200420gitdb6cd2375.fc31.x86_64

Steps to reproduce

  1. Configure password history policy as bellow:
    passwordHistory: on
    passwordInHistory: 3
  2. Change the password 3 times without time.sleep()
  3. Try to change the password to the first password that was added to passwordHistory

Actual results

Password is accepted

Expected results

Password should be rejected with Constraint Violation error

I wonder if this means we need password change in a be-txn, and then with lmdb/other we'll get proper serialisation ...

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4

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/4099

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
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.