#49715 dsidm should work on any entry, not just nsUserAccounts
Closed: wontfix 2 years ago by vashirov. Opened 3 years ago by mreynolds.

Issue Description

Right now dsidm only works with entries created by dsidm. An existing database will not be able to use dsidm to access it. The tool uses very strict search filters using the MUST attributes/objectclasses. The tool should be more robust to work with a variety of entries.

The account command works for this use case, it works on anything that could be an account. So I think this is already solved?

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

3 years ago

Metadata Update from @vashirov:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 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/2774

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)

2 years ago

Login to comment on this ticket.