SSL config should use model sockets

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48199

• Created at 2015-06-12 20:17:40 by rmeggins (@richm)
• Assigned to nobody

---

When changes are made to SSL configuration over LDAP, we should immediately store those changes in a model socket. In slapd_ssl_init2, when calling SSL_ImportFD, we should use the model socket argument. Then we don't have to do all of the SSL configuration in slapd_ssl_init2, that will be done by calling SSL_ImportFD with the model.

At startup, we should create the model socket from the configuration entries, then use the model socket to create the SSL listener sockets.

I'm not sure what we can do dynamically with SSL listener sockets. It may be possible to stop listening (remove the SSL listener fds from the poll list), then use SSL_ReconfigFD to reconfigure them with the latest SSL settings, then add them back.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2016-05-13 00:44:25

Per triage, push the target milestone to 1.3.6.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 22:53:55

Metadata Update from @nhosoi:

• Issue set to the milestone: 1.3.6.0

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:30:50

Metadata Update from @mreynolds389:

• Custom field component reset (from Security - SSL)
• Issue close_status updated to: None
• Issue set to the milestone: 1.4 backlog (was: 1.3.6.0)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-10-18 21:58:55

Metadata Update from @mreynolds389:

• Custom field component adjusted to None
• Custom field reviewstatus adjusted to None
• Issue tagged with: RFE

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-05-27 21:30:54

Metadata Update from @mreynolds389:

• Issue priority set to: normal (was: major)
• Issue set to the milestone: FUTURE (was: 1.4 backlog)