Hi Sriram,
Jira has supported OpenJDK for a bit now - 7.13 and all versions of Jira 8 support OpenJDK. We also bundle AdoptOpenJDK with our installers (Jira 8.3 and above), so installations/upgrades to versions 8.3 or above may already be using AdoptOpenJDK.
When changing JDKs, you'll need to consider what certificates you've already imported to your keystore. By default, the keystore holds certificates for most public Certificate Authorities (GoDaddy, Verisign, Comodo, GeoTrust, etc). You'd need to import certificates in these circumstances:
- You want Jira to connect to a server that uses a certificate signed by an internal authority (example: LDAPS, Exchange, etc - most common in Windows environments), a public authority that isn't in the default Java keystore, or a self-signed certificate. In this case, you'll import the public certificate using these instructions.
- You are serving HTTPS/TLS from Jira directly - your users connect to Jira over HTTPS and their connection is not terminated at a reverse proxy. In this case, you'll need to import the public and private certificates into the keystore. Instructions for that are in this document - Running Jira applications over SSL or HTTPS .
I would recommend that in case #2 - serving Jira over HTTPS, that you instead look at using a reverse proxy such as nginx or Apache to terminate the TLS connection between the server and the client's browser. Reverse proxies are a bit easier to set up and offer a little more performance than serving TLS from Tomcat (Jira's application server) directly. They have the added benefit of moving the TLS termination out of the application itself, so you won't need to re-import private certificates when looking at switching JDKs or doing a Jira upgrade.
Here to help if you've got more questions!
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.