Hi @Supun Ranatunge,

I believe you have worked on some of these HTTPS requirements. Are you able to assist here?

Kind regards,

Lee Pinchbeck

Hi @Lee Pinchbeck 

This is in fact about the case created by Supun. I’ve contacted Jon Reid from R&D and he mentioned the only method supported by RnD is to run the installer. Since you don't have to re-run the database upgrade, you just have to re-install the same version of the app server and mobile service you already have, specifying https instead of http. It should take 5 minutes per app server/mobile service.

Thanks & Best Regards,

Hushan Hasarel

@Lee Pinchbeck , thank you very much for the ping.

Seems I had missed this post, my apologies. My colleague the other “Supun Ranatunge” had been tagged to the post 

As I recall we did mention to the customer that the recommended method is to use the installer & mentioned there won’t be any changes to the database.

However their team was more concerned about several client files they had customized in some way, and was keen on not running the installer.

On the topic of manually changing files:

It’s always best to follow the R&D recommended method, which is using the installer.

But for learning purposes it would be handy to know which client files to change manually in order to configure https on an FSM instance.

So any reply/suggestion/discussion is welcome in this thread 

Thanks & Best Regards,

Supun Ranatunga.

Have you been able to pin point the changes need in the configs files?

Thank you,

Charalampos