SSL - Reduction in Validity - How to Handle

Question

Hi,We’re using IFS Apps 10 with external HTTPS terminated at an Azure Application Gateway, and the same wildcard certificate is also installed on our IFS middleware VM for client signing during Reconfigure. With certificate lifetimes reducing and automated renewal becoming more common, I’m trying to understand how other customers handle this, has anyone figured a way of either not requiring a reconfigure to pickup the new certificate or a way of automating this reconfigure OOH?If the certificate is automatically renewed and updated on both the gateway and the VM (same private key if possible), IFS still seems to require a manual Reconfigure to pick up the new certificate (in theory so far) for client signing. Has anyone successfully automated this end‑to‑end, or found a reliable method for IFS to detect and use the renewed certificate without manual intervention?Please note, we’re automatically signing below.

ashen_malaka_ranasinghe · Answer

Hi ​@TmRyk,We use the same F1Mage client-signing configuration ("Automatically sign client with F1Mage" + "Use same certificate as web server"), and my understanding is that Apps 10 picks up the certificate during Reconfigure rather than dynamically from the certificate store. Because of that, I am not aware of a supported way for Apps 10 to automatically detect and start using a renewed certificate without running a Reconfigure.If your renewal process replaces the certificate while keeping the same store location, alias, and private key, it may be worth testing whether Apps 10 continues to work without reconfiguration, but I have not seen any official confirmation that this is supported.If anyone has fully automated this, I would expect the solution to involve automating certificate deployment followed by a silent/scheduled reconfigure during an out-of-hours maintenance window rather than avoiding the reconfigure step altogether.

Did you find what you're looking for? If not:

Sign up

Login to the community