01-12-2022, 07:50 AM
According to your post seems that you are considering an Indy based stand alone application. This application can't use 2 different certificates. Indy relies on OpenSSL and a single certificate must be loaded by each instance of the HTTPS server.
Having said that, seems to me that you have 2 options:
1- use a reverse proxy (e.g. Apache) on top of your IW application. If you have a single application instance, this won't be simple I'm afraid. Better if you have 2 different instances
2- Install 2 instances of the same IW application created as Http.sys, registering one for each domain. The certificates are registered in Windows (using IWCertificateManager which is installed with IntraWeb), one for each domain. Both instances are independent but they can share the same port 443 which is exactly what you want.
Having said that, seems to me that you have 2 options:
1- use a reverse proxy (e.g. Apache) on top of your IW application. If you have a single application instance, this won't be simple I'm afraid. Better if you have 2 different instances
2- Install 2 instances of the same IW application created as Http.sys, registering one for each domain. The certificates are registered in Windows (using IWCertificateManager which is installed with IntraWeb), one for each domain. Both instances are independent but they can share the same port 443 which is exactly what you want.