#107 Org Chart passes Locator a CN rather than the DN
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by mkosek.

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

Description of problem:

The Org Chart can be configured to support an external "locator" application
(url-locator-base in config.txt).  However, the "org" application passes the
locator a cn, which is not guaranteed to be unique within the directory.  As a
result, the locator may locate the wrong person.  Could org be changed to pass
the dn of the person to be located, rather than a cn?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I believe the relevant lines of $FDS_BASE/clients/orgchart/bin/org are
1495-1515, in the function print_topmost_box().

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @nkinder:
- Issue set to the milestone: FUTURE

7 years ago

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

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/107

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