How does one allow IIS (8 in my case) to handle SSL and not Tomcat?

[Richard Barbre]

I have read some where that using IIS to proxy request to Tomcat, that IIS can handle all of the SSL encryption / decryption. What changes need to be made in the server.xml to insure that generated links in Jira show the https and not the http?

[Pedro Souza · Accepted solution]

You need to add the conector to your serverl.xml:

<!-- Proxy Connector with values for scheme, proxyName and proxyPort -->
        <Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true" 
            scheme="https" proxyName="proxy.yourproxy.com" proxyPort="443"/>

Cheers,

Pedro Souza.

[Richard Barbre]

Ok, I assume that the 2 main items there are the scheme and proxyport. Now what about the base URL in the Jira Settings?

[Pedro Souza]

After configuring the connector, you will see a notification in your JIRA pages, asking for update the base URL to use the https, then you just need to update it directly on the general settings.

[Richard Barbre]

Thank you for your responses. Now, using the IIS ARR and UrlRewrite modules; would I change the rule to https://localhost:8443/{R:0}?

[Richard Barbre]

Ok, Pedro basically answered this question. Disregard my last comment, it is incorrect. The URL rewrite rule remains the same as a standard site without the SSL https.