HI Team,
we are planning to upgrade our JIRA instance which is on 7.13 to version 8.13.2 and post the upgrade , we are planning to configre ssl with JIRA.
The atlassian document that i referred looks little confusing .Could you please let us know the steps of self signed ssl configuration with JIRA.
It would be really helpful.
there are, indeed, several options. Based on experience the approach with a separate >Reverse Proxy< (for example, using Apache) works best:
https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html
The reverse proxy will be responsible for terminating the SSL connections.
There is also the option to do it in JVM directly - but from what I found during the years, this is a pain to configure.
Yes, even setting up a reverse proxy is not easy as typing one command in and everything would be running - but with some effort and some time considering how the configuration is meant to be, it is doable.
Which part of documentation do you especially find confusing?
Cheers,
Daniel
Hi Daniel ,
My JIRA is configured with IIS as proxy and apache/tomcat is the application container . The self signed certificate will be provided to us by the server team. My query is how i can change http to https i.e. configure SSL on JIRA with this setup using the self signed certificate. I have referred Running JIRA applications over SSL or HTTPS | Administering Jira applications Data Center and Server 7.3 | Atlassian Documentation this document.
Could you please let me know if any changes needs to be done in server.xml file as the JIRA is standalone setup and i being the newbie in this configuration am totally unaware of the steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is an anwer from Nic above - kindly refer to this one, where you will find all needed info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have not told us how you are trying to do SSL with the service, or what documentation you have tried to use and where you have got stuck with it.
Could you describe what you're doing and where you got stuck with the doc?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
We will be implementing SSL on the coming weekend. Our JIRA instance is a standalone JIRA installed on windows as JIRA service with IIS used as proxy . the certificates we will be getting are self signed certificate ,
i referred the URL Running JIRA applications over SSL or HTTPS | Administering Jira applications Data Center and Server 7.3 | Atlassian Documentation
Could you please let me know what all config changes we needt to do considering the server.xml or other fies , because this document looks little complicated .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The config changes you need to do for SSL on the Tomcat side are in that doc.
But you say you want to use IIS as a proxy, which is often done so you don't have to do SSL on the Tomcat. IIS does all the SSL work and then talks to Jira (with no-one else allowed to talk directly to Jira)
For the IIS SSL, start at https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
when I did mine, I used let's encrypt SSL following these steps on ubuntu server and entering the details (i.e. my email address) on the prompts. I had apache httpd running and configured it via a proxy.
add-apt-repository ppa:certbot/certbot
apt-get update
apt-get install python-certbot-apache
certbot --apache -d jira.example.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.