Hi guys,
When we install our software we currently just support HTTP binding on our installed website in IIS, but the software does support HTTPS. If HTTPS is required then the user has to configure the system manually after installation is completed, by installing a certificate, adding an SSL binding to the website, and updating the Web.config file for the application.
We would like to automate this process now if possible via the installer. I can see that it is possible to support an HTTPS binding in IIS, and to ask for a PFX certificate from the user as well, which meets our main requirements, however there are some requirements that I can't find an answer to:
- Is it possible to declare an HTTPS binding in Advanced Installer that is conditional on some other installer property? We don't want to force all installations to use SSL, so the SSL binding and PFX installation should only happen if the user has selected HTTPS as their preferred protocol.
- Additionally we may want to disable the HTTP binding as well, so this would also need to become conditionally installed based on installer properties as well, is this possible?
- Is the certificate automatically uninstalled as well? Or does it remain on the computer?
Thanks!
Sam
FOLLOW US
Get the latest news in Application Packaging