Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1589144
Description of problem: The attribute shadowWarning is not returned if the passwordWarning value is lower than 86400 seconds (1 day). Version-Release number of selected component (if applicable): # rpm -qa | grep 389-ds-base- 389-ds-base-debuginfo-1.3.7.5-18.el7.x86_64 389-ds-base-1.3.7.5-13.el7.x86_64 389-ds-base-libs-1.3.7.5-13.el7.x86_64 # How reproducible: Always. Steps to Reproduce: 1. Set the passwordWarning value to 86400 or higher: # ldapsearch -xLLL -p <PORT> -h <HOST> -b "cn=config" -D"cn=Directory Manager" -W -sbase passwordWarning Enter LDAP Password: dn: cn=config passwordWarning: 86400 # A search will return the shadowWarning attribute: # ldapsearch -xLLL -p <PORT> -h <HOST> -b "ou=People,o=Test" -D"cn=Directory Manager" -W "uid=tmorris" shadowWarning Enter LDAP Password: dn: uid=tmorris,ou=People,o=Test shadowWarning: 1 # 2. Set the passwordWarning value lower than 86400: # ldapmodify -x -D"cn=Directory Manager" -W -p <PORT> -h <HOST> Enter LDAP Password: dn: cn=config changetype: modify replace: passwordWarning passwordWarning: 86399 modifying entry "cn=config" # No value for is returned for shadowWarning: # ldapsearch -xLLL -p <PORT> -h <HOST> -b "ou=People,o=Test" -D"cn=Directory Manager" -W "uid=tmorris" shadowWarning Enter LDAP Password: dn: uid=tmorris,ou=People,o=Test # Actual results: shadowWarning is only generated if the passwordWarning value is higher or equal to 1 day. Expected results: shadowWarning should be returned as long as passwordWarning is defined. Additional info:
Metadata Update from @vashirov: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1589144
PR https://pagure.io/389-ds-base/pull-request/50094
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
0bc51f365...967d0aa2b master
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.9 (was: 0.0 NEEDS_TRIAGE)
Please cherry-pick to 1.3.9
b831fe0d3..c497fd870 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Mark, I think 967d0aa2b4ec283c0c9ef69b5781bf236af27cc7 also needs to be cherry picked
c497fd870..0ef038332 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
Mark, I think 967d0aa also needs to be cherry picked
Done, thanks!
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/3150
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)