How Can I Redirect HTTP to HTTPS with IIS Integration?

 
Author
Message
Elite SysAider
151
 
Hello,

We are using IIS Integration with Sysaid On-Premise. WE have it working on both port 80 and 443. What is the easiest way to redirect the HTTP site to HTTPS? I've tried a couple methods, but none seem to work.

We are running on Windows Server 2012 R2 with IIS and Sysaid 15.4.

Thank you!
SysAid Product Manager Community Manager
5067
 
Hi Chris,

Can you check what appears in your Site Bindings in IIS? Does HTTPS with port 443 appear in the list? If not, please add it and check if it produces the desired effect. If still not - remove the http port 80 from the bindings and check if this resolves the issue.

Cheers,
Danny
Elite SysAider
151
 
Both ports are in the bindings. I can get to the site using both HTTP and HTTPS. However, if someone accesses the site using HTTP, I want them to get redirected to HTTPS so that all comms are always secure.
SysAid Product Manager Community Manager
5067
 
From the information I've received from my colleague, you can try removing the http-80 binding and check if the website automatically redirects to https. Please let me know if this works.

Edit: This solution is incomplete, the post below by SBM.ChrisW has the full solution.

Cheers,
Danny

This message was edited 4 times. Last update was at Mar. 27, 2016 02:31 AM

Elite SysAider
151
 
I have resolved this issue and wanted to make sure the answer is out there for others that may have this trouble.

Simply removing port 80 from the bindings does not help because then you get a 403 site not found because the site simply will not answer on port 80. The desired result is for the user to hit port 80 (because nobody ever types https) and then get redirected to a secure 443 channel.

We tried using the HTTP Redirect feature within IIS on the Sysaid website. This did not work because of some sort of issue with the tomcat webserver configuration. Every time you would hit http://helpdesk.website.com it would redirect you to https://helpdesk.website.com/isapi_redirect_64.dll.

So what we ended up doing is removing the port 80 binding from the Sysaid IIS site. Then we put the same host header on the default website in IIS which was already configured for port 80. At that point we were able to use the HTTP Redirect feature in IIS to redirect from the default IIS website to the IIS Sysaid Jakarta site on port 443 without an issue.

Problem solved.

This message was edited 2 times. Last update was at Mar. 25, 2016 11:57 AM

SysAid Wiz
271
 
This is awesome, thanks!
SysAid Product Manager Community Manager
5067
 
Great, thanks for the update! I have edited my post to point to your solution.

Cheers,
Danny
SysAider
24
 
SBM.ChrisW wrote:I have resolved this issue and wanted to make sure the answer is out there for others that may have this trouble.

Simply removing port 80 from the bindings does not help because then you get a 403 site not found because the site simply will not answer on port 80. The desired result is for the user to hit port 80 (because nobody ever types https) and then get redirected to a secure 443 channel.

We tried using the HTTP Redirect feature within IIS on the Sysaid website. This did not work because of some sort of issue with the tomcat webserver configuration. Every time you would hit http://helpdesk.website.com it would redirect you to https://helpdesk.website.com/isapi_redirect_64.dll.

So what we ended up doing is removing the port 80 binding from the Sysaid IIS site. Then we put the same host header on the default website in IIS which was already configured for port 80. At that point we were able to use the HTTP Redirect feature in IIS to redirect from the default IIS website to the IIS Sysaid Jakarta site on port 443 without an issue.

Problem solved.



Works like a charm!! Thanks!
SysAider
31
 
How can we do this ? <<So what we ended up doing is removing the port 80 binding from the Sysaid IIS site>>

Kind Regards,

Rudi
Elite SysAider
151
 
If you have Sysaid configured with the IIS integration, you simply go into bindings to the the website and remove port 80.

You basically have to have two websites. On for http that simply has code on it to redirect to your https site.

One with the SysAid IIS integration configured for https.