#50711 `dsconf security` lacks option for setting nsTLSAllowClientRenegotiation attribute
Closed: wontfix 2 years ago by mreynolds. Opened 2 years ago by mhonek.

Issue Description

dsconf security is not able to handle nsTLSAllowClientRenegotiation attribute. This should be implemented.

Package Version and Platform

1.4

Steps to reproduce

  1. dsconf security set -h
  2. Observe the output does not contain the attribute.

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

2 years ago

Yep, this seems really quick to add.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

2 years ago

Metadata Update from @mhonek:
- Issue assigned to mhonek

2 years ago

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

2 years ago

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

2 years ago

@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)?

@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

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.

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.

Metadata
Related Pull Requests