dsconf security is not able to handle nsTLSAllowClientRenegotiation attribute. This should be implemented.
dsconf security
nsTLSAllowClientRenegotiation
1.4
dsconf security set -h
The original implementation ticket: https://pagure.io/389-ds-base/issue/49303
Metadata Update from @mhonek: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Yep, this seems really quick to add.
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
Metadata Update from @mhonek: - Issue assigned to mhonek
We should also use this ticket for adding this setting to the UI, so don't close it out yet
Commit 7b1144e relates to this ticket
Cherry-picks of 7b1144e: 994a109..d513014 389-ds-base-1.4.0 -> 389-ds-base-1.4.0 af44acd..2a64658 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
Metadata Update from @mhonek: - Issue tagged with: CLI, Cockpit
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
@mreynolds As per your comment above I kept this open so that this gets implemented in the WebUI, too. Where is this fixed (master does not seem to contain)?
I just added it to the web UI via https://pagure.io/389-ds-base/pull-request/50893
Cool, thank you!
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/3766
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: fixed)
Login to comment on this ticket.