I have two seperate webapps running on HTTPS protocol (listening on port 443) using 2 different certicates.
When users access the first HTTPS webapp the browser will prompt them to accept the certificate once, their sessions will be valid throughout the pages in the same webapp. But then when I try to portforward them to another HTTPS webapp through another port, let's say 9800, within the same IP, the second webapp page will prompt the user to accept the new certificate of it (which it should) and then the session of the first webapp will no longer be valid. (The session id has changed).
To make things clear here's the portforwarding process:
Any advice from the experts would be helpful. Maybe some workarounds too. Thanks in advance.