#47518 [RFE] Support an alternative way of exporting updates in automember export updates task
Closed: wontfix 3 years ago by mreynolds. Opened 10 years ago by akrivoka.

Right now, the way the automember export updates task works is, it creates an LDIF file with the changes. This LDIF file is created with ownership/privileges of the dirsrv user, which makes is difficult to be read by other users on the system, which is sometimes needed. It would be useful to have an alternative way of accessing the results of the automember export updates task. (Maybe the results can be stored somewhere in LDAP, for easier access?)

This RFE stemmed from this email thread on the freeipa-devel mailing list:
https://www.redhat.com/archives/freeipa-devel/2013-September/msg00188.html


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

7 years ago

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

3 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/855

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