[OPENDJ-7207] Retest the distribution example Created: 18/May/20  Updated: 31/Jul/20  Resolved: 31/Jul/20

Status: Done
Project: OpenDJ
Component/s: documentation
Affects Version/s: 7.0.0
Fix Version/s: 7.0.0

Type: Task Priority: Critical
Reporter: Mark Craig Assignee: Miroslav Meca
Resolution: Fixed Votes: 0
Labels: Verified

Issue Links:
Relates
relates to OPENDJ-7291 Provide a debugging tool for connecti... Dev backlog
relates to OPENDJ-7298 Move the AM CTS admin entry out of th... Dev backlog
is related to OPENDJ-7306 Spurious message when importing LDIF Dev backlog
is related to OPENDJ-6881 Review default ACI policies shipped w... QA Backlog
Epic Link: Miscellaneous 7.0
Story Points: 3
Dev Assignee: Mark Craig
QA Assignee: Miroslav Meca

 Description   

The example demonstrating data distribution is not automatically tested, yet.

Either retest https://ea.forgerock.com/docs/ds/config-guide/proxy.html#pattern-data-distribution-example manually, or integrate it into the automated tests.



 Comments   
Comment by Mark Craig [ 09/Jun/20 ]

Marking this as critical. Since the example is not part of the integrated doc tests, and the server configuration has changed, the example is probably broken as is.

Comment by Mark Craig [ 17/Jun/20 ]

While trying to work out how get the CTS distribution example working with a server build off master from earlier today, I am stumped.

The proxy user can bind (SASL external) when going directly to the backend DS/RS servers.

When trying through the proxy, the result is invalid credentials (49) with a message, "Unable to bind to the Directory Server because no such user exists in the server". From the code, it looks like that message is only returned when trying to bind on a local backend, but maybe I'm reading it wrong.

The patch so far is https://stash.forgerock.org/projects/OPENDJ/repos/opendj-docs/pull-requests/1463. Perhaps it will make more sense later if I back off for now.

I wonder where I might be able to see what's happening to the routing.

Seeing Matt's PR for OPENDJ-7276 also reminds me about the missing access control. I wonder if that has anything to do with this issue.

Comment by Mark Craig [ 19/Jun/20 ]

If OPENDJ-7298 is not fixed, the script installing the DSs should move the CTS Admin user out of the data, and update the information needed to configure AM.

Generated at Wed Oct 21 10:49:25 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.