#49033 [RFE] setup-ds.pl - Mismatched password on first attempt does not prompt to enter original password again
Closed: wontfix 3 years ago by mreynolds. Opened 7 years ago by nhosoi.

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

Description of problem:
The issue is that, in setup-ds.pl when you enter a password(and say you made a
mistake) and you confirm with another password, you are always again prompted
for only the confirmation password.

Version-Release number of selected component (if applicable):
[root@test dirsrv]# rpm -qa | grep 389
389-ds-base-libs-1.3.5.10-1.el7.x86_64

How reproducible:
[root@test slapd-test]# setup-ds.pl
<snip>

Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
The passwords do not match.  Please try again.

Password (confirm):
The passwords do not match.  Please try again.

Password (confirm):

</snip>

eg. In the above, I have to set my instance password as test1234
password: tst1234
password (confirm): test1234

This gives an error "The passwords do not match.  Please try again.
and it again it ask for the password (confirm)
Password (confirm): " . But, this will never let me enter my expected password
afresh.

Expected results:
It should again ask for new password first and then the password again to
confirm.
Even IPA Server installer allows you to re-enter the original password if you
get a password mismatch.

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6.0

7 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)

6 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.7.0 (was: 1.3.7 backlog)

6 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4 backlog (was: 1.3.7.0)

6 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 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/2092

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.

Metadata