Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI - When password prompt is requested for repl status, it uses it for all servers #5971

Closed
droideck opened this issue Oct 27, 2023 · 2 comments · Fixed by #5972
Closed
Assignees
Labels
needs triage The issue will be triaged during scrum

Comments

@droideck
Copy link
Member

droideck commented Oct 27, 2023

Issue Description
dsconf replication status is failing with 'Invalid credentials' when the password of the Directory Manager is not identical on servers.

Steps to Reproduce
Steps to reproduce the behaviour:

  1. Create 2 RHDS instances
  2. Do not use identical passwords for the Directory Manager
  3. Enable replication and create a simple "Supplier ==> Consumer" topology
  4. Run the "dsconf replication status" command without specified password option (prompt will be requested)

Actual results
The command fails with 'Invalid credentials' errors.

Expected results
Report is printed

Additional context
Replication is configured for the suffix "dc=example,dc=com" on both supplier_1 and supplier_2 instances.

  • supplier_1 ( 2389 / 2636 )
  • supplier_2 ( 4389 / 4636 )
  1. Using the same password ( secret12 ) for the Directory Manager on both servers:
# dsconf -D "cn=Directory Manager" ldap://localhost:2389 replication status --suffix "dc=example,dc=com"
Enter password for cn=Directory Manager on ldap://localhost:2389: 
{'agmt-name': ['supplier_1-to_supplier_2'], 'replica': ['XXXX:4389'], 'replica-enabled': ['on'], 'update-in-progress': ['FALSE'], 'last-update-start': ['20231003180910Z'], 'last-update-end': ['20231003180910Z'], 'number-changes-sent': ['100:1/0 '], 'number-changes-skipped': ['unavailable'], 'last-update-status': ['Error (0) Replica acquired successfully: Incremental update succeeded'], 'last-init-start': ['20231003180124Z'], 'last-init-end': ['20231003180127Z'], 'last-init-status': ['Error (0) Total update succeeded'], 'reap-active': ['0'], 'replication-status': ['In Synchronization'], 'replication-lag-time': ['00:00:00']}
#
  1. Change the password on supplier_2 to secret123:
# dsconf -j ldapi://%2fvar%2frun%2fslapd-supplier_2.socket config replace nsslapd-rootpw=secret123
  1. Run the command again:
# dsconf -D "cn=Directory Manager" ldap://localhost:2389 replication status --suffix "dc=example,dc=com"
Enter password for cn=Directory Manager on ldap://localhost:2389: 
Error: Unable to get lag time: {'msgtype': 97, 'msgid': 1, 'result': 49, 'desc': 'Invalid credentials', 'ctrls': []}
#
@droideck droideck added the needs triage The issue will be triaged during scrum label Oct 27, 2023
@droideck droideck self-assigned this Oct 27, 2023
@droideck
Copy link
Member Author

droideck commented Oct 27, 2023

I think I know how to fix it quickly. I'll work on that.

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2217641

droideck added a commit to droideck/389-ds-base that referenced this issue Oct 27, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is not identical on servers.
Ask for each instance's password separently.
Expand the help message in CLI for replication and agreement status commands.

Fixes: 389ds#5971

Reviewed by: ?
droideck added a commit to droideck/389-ds-base that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is not identical on servers.
Ask for each instance's password separently.
Expand the help message in CLI for replication and agreement status commands.

Fixes: 389ds#5971

Reviewed by: ?
droideck added a commit to droideck/389-ds-base that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is not identical on servers.
Ask for each instance's password separently.
Expand the help message in CLI for replication and agreement status commands.

Fixes: 389ds#5971

Reviewed by: ?
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
droideck added a commit that referenced this issue Oct 31, 2023
Description: dsconf replication status is failing with 'Invalid credentials'
when the password of the Directory Manager is different on servers.
Ask for each instance's password separately.
Expand the help message in CLI for replication and agreement status commands.

Fixes: #5971

Reviewed by: @tbordaz (Thanks!)
@droideck
Copy link
Member Author

176b5b5..eaaf93f 389-ds-base-2.3 -> 389-ds-base-2.3
8884fcf..a8b20dd 389-ds-base-2.2 -> 389-ds-base-2.2
6833400..32f5ae9 389-ds-base-2.1 -> 389-ds-base-2.1
2aac04b..f79927a 389-ds-base-2.0 -> 389-ds-base-2.0
2ded197..54875d2 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant