The traffic servers reference the CA file via proxy.config.ssl.CA.cert.filename. from my [bad] reading of the code the config option is read in SSLconfig.cc. it is unclear if the file is read when the daemon stars or if it is read on demand @ema is investigating
The old certificate expires Jun 29 19:36:29 2020 GMT
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | jbond | T236277 Extend Puppet CA Expiry date | |||
| Resolved | jbond | T237259 Document all uses of the puppetCA certificate | |||
| Resolved | jbond | T240330 Check if traffic servers need restarting/reloading post CA change |
ema, confirmed that the traffic servers did need a restart which has now been preformed