-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
Moderate
-
rhel-idm-ds
-
0
-
False
-
False
-
-
Yes
-
None
-
None
-
Automated
-
Enhancement
-
-
Proposed
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
- Problem Statement Support updating/renewing TLS certificate without restarting slapd
- Presently we require a service restart for the update: https://docs.redhat.com/en-us/documentation/red_hat_directory_server/12/pdf/securing_red_hat_directory_server/Red_Hat_Directory_Server-12-Securing_Red_Hat_Directory_Server-en-US.pdf
Sections 1.3 and 1.4
- Presently we require a service restart for the update: https://docs.redhat.com/en-us/documentation/red_hat_directory_server/12/pdf/securing_red_hat_directory_server/Red_Hat_Directory_Server-12-Securing_Red_Hat_Directory_Server-en-US.pdf
Explanation of Cu case:
I'm hoping however that it would be possible for RHDS to support some method of reloading the TLS certificate/key without stopping and restarting the service. If not via something simple like SIGHUP, perhaps a task entry like reloading the schema could trigger slapd to reload the TLS key & certificate and then use it for new client connections.
(This would enable something using a ACME renewal process to call a helper script to easily update the certificate and make it active without needing to coordinate the process across the pool of load-balanced replicas and wait to drain connections from the instance.)
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- Renew certificate
- Have alternatives for admins other than the currently expected, # dsctl instance_name restart
- links to