Currently, if I need to update the x509 Certificate for SIEGATE, this would require all parties to schedule the same downtime during this certificate change. This will be an operational nightmare. It would be better if a single connection can have 2 valid client certificates at a time. Then I could notify all parties that on a specific date, I'll be changing my server certificate. This would give them time to add the .cer file to their remote SIEGate servers before the change over.
Currently, if I need to update the x509 Certificate for SIEGATE, this would require all parties to schedule the same downtime during this certificate change. This will be an operational nightmare. It would be better if a single connection can have 2 valid client certificates at a time. Then I could notify all parties that on a specific date, I'll be changing my server certificate. This would give them time to add the .cer file to their remote SIEGate servers before the change over.