Apache SSL for JIRA

[gil]

This link describe how to configure Apache as proxy server for JIRA: http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache+using+SSL?focusedCommentId=268730472&#comment-268730472

So I have everything set up and working with this configuration: Client Browser --> HTTPS --> Apache proxy --> HTTP --> Tomcat/JIRA. However, with this setup, JIRA won't be able to serve both SSL & non-SSL incoming requests. I think that's due to these attributes in tomcat:

scheme="https"
proxyName="server1"
proxyPort="443"

How do I make JIRA to serve both ssl & non-ssl via the apache proxy server?

[Thomas Peter Berntsen]

Gil, you should try to create two Virtual Host directives in your Apache HTTPD configuration and two Connectors in your Tomcat (running JIRA). One pair for HTTP and one for HTTPS, that is.

Remember to change the connector port assignment and proxied port in the Apache HTTPD Virtual Host configuration accordingly for the new/additional pair. E.g. one connector running port 8080 and one 8081 (if nothing else is running on that port).

But beware: JIRA only really understands how to respond to requests to one hostname (and one scheme) really well:

The base URL of this JIRA installation. You can only configure JIRA to respond to a single URL and this setting must match the URL that your users request for accessing your JIRA site. You cannot (for example) have a different hostname or URL for internal and external users. This is especially important for JIRA 4.0.x or higher, as any mismatch between this Base URL setting and the URL requested by your JIRA users will cause problems with dashboard gadgets. This URL is also used in outgoing email notifications as the prefix for links to JIRA issues.

From: http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options

Having several hostnames or schemes (HTTP and HTTPS) can be an invitation to strange bugs starting to show up, so I would always recommend one hostname and one scheme. And, while we're at it: go for security and thus HTTPS. ;-)

Cheers,
Thomas

[AndreyevM]

Holly smoke, such complicated thing!

Did you run JIRA in Tomcat or standalone?

I think my setup is pretty clear:

1. JIRA standalone listening only to AJP port (8009)
2. Apache + mod_jk (must be compiled) and worker file properties
3. 2 virtual hosts, each one with a jkmount to the same worker

Helped? ;-)