#214 Adding Replication agreement should complain if required nsds5ReplicaCredentials not supplied
Closed: wontfix None Opened 9 years ago by rmeggins.


Description of problem:
When adding a replication agreement with a bind method of DIGEST-MD5, where
bind password is required - if nsds5ReplicaCredentials is not supplied, the
agreement should not be added and an appropriate error message returned.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install two servers.
2. Add replication manager to both servers
3. Enable replication.
4. Add replication agreement with bind method of DIGEST-MD5 but do not add the
nsds5ReplicaCredentials attribute.

Actual results:
Replication agreement is successfully added, but replication bind fails.

Expected results:
Adding the invalid replication agreement should fail with appropriate error.

Additional info:

batch move to milestone 1.3

Only SIMPLE and SASL/DISGEST-MD5 require bind DN's and passwords.

git merge ticket214
Updating 540b278..d4327cf
ldap/servers/plugins/replication/repl5_agmt.c | 23 +++++++++++++++++++++--
1 files changed, 21 insertions(+), 2 deletions(-)

git push origin master
Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 1.29 KiB, done.
Total 7 (delta 5), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
540b278..d4327cf master -> master

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.11

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

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 (was: Fixed)

a year ago

Login to comment on this ticket.