If exporting DIT which contains an entry with an attribute value includes trailing whitespaces onto a console machine, the attribute value is not base64 encoded.
Note: if it is exported to the server machine, it is base64 encoded as expected.
Per weekly meeting: We should fix this for 10.1 if it's not too difficult.
When the console is connected to a remote server, and you choose to export to the console machine, the console basically does a search for every entry on the remote backend/suffix. The underlying issue is how the ldapjdk processes the search results. The DS console is not manipulating the results.
Closing as won't fix since customer closed case and there are workarounds.
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 389-admin,console 1.1.44
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/2000
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.