When the TLS certificate expires (yearly), it must be deployed manually on all servers, from the PCAs on downward. When you have a large server count (50, for example) this process is time consuming and error prove (as it's a manual process).

To make this process more manageable, TMS should be enhanced to pre-deploy the certificate to all servers, including the PCAs, and then broadcast an update schedule to all servers. The servers would then self-update at their proscribed time.

The old certificate would be retained (not overwritten) and a provision for rollback would be provided. Possibly, TMS would retain non-SSL communication capabilities for validation and triggering an administrator controlled rollback.

For example:

3:00am: half of PCAs and HBRs update

3:05am: The other half update

3:10am: All canisters update

3:15am: All archive servers update

3:20am: All remaining update (portal/report/data collection/pre-agg, etc)

The update process must be very reliable. Reboot should not be required. Ideally service restart should not be required (Socket reconnect/retry).

Search tags: TLSTool.exe, TCXcert.pfx, tealeaf.crt, tealeaf.p12, ServerCertPath