Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Installing a new Wildcard SSL Certificate on an existing Confluence Server

So, we are currently running a Confluence Server and the certificate has expired.  It was using a certificate specific to the url.  Since that time we have obtained a wildcard certificate and would like to install that on Confluence.  There are steps for configuring Confluence to use SSL, however as a "novice" I can't determine what parts apply to "replacing" a certificate.  We have the certificate already and we know the password assigned to it.

  1. We don't need to generate an CSR do we?
  2. https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html is the article that we are looking at.
  3. Do we have to create a self signed certificate in our scenario?
  4. In the section below from the instructions is the CN the hostname/ComputerName of the server, or the URL/Domain Name used for the confluence site, in our case they are not the same.

"Follow the prompts to specify your name, organisation and location. This information is used to construct the X.500 Distinguished Name (DN) of the entity. The CN ("What is your first and last name?") must match the fully-qualified hostname of the server running Confluence, otherwise Tomcat will not be able to use the certificate for SSL. For example for a Confluence running on a server named "confluence.example.com":
CN=confluence.example.com, OU=Java Software Division, O=Sun Microsystems Inc, C=US"

  1. Also in the comments section there is information about using a PKCS #12 file and only editing 3 lines of code.  Does this work?  Can I really just skip all of the other stuff and edit 3 lines in the server.xml file?

JR

2 answers

1 vote
Guilherme V. Atlassian Team Oct 02, 2015
Hey buddy!
  1. We don't need to generate an CSR do we?
    You don't need to create a new one, you can authenticate the same CSR with your C.A. Just don't forget to import it in the keystore.
  2. https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html is the article that we are looking at.
    Alright, that's the best documentation for it smile.
  3. Do we have to create a self signed certificate in our scenario
    There's no problem in creating a new certificate. But you'll have to authenticate it later with the C.A
  4. In the section below from the instructions is the CN the hostname/ComputerName of the server, or the URL/Domain Name used for the confluence site, in our case they are not the same.
    I've never tested with this scenario, but I think they need to be the same. Not sure sad
  5. Also in the comments section there is information about using a PKCS #12 file and only editing 3 lines of code.  Does this work?  Can I really just skip all of the other stuff and edit 3 lines in the server.xml file?
    That's only for GoDaddy and Verisign, so you're probably using one of them, right? Never tested the steps described by that user, but i noticed that it worked for some other customers. Test it in a staging instance before smile.

These commands worked for us on a .pfx exported from IIS (where the wildcard CSR was generated). Be sure to use the same passphrase for the keystore as that used to sign the CSR!

/opt/jdk1.8.0_45/jre/bin/keytool -importkeystore -srckeystore <your-wildcard-cert>.pfx -srcstoretype pkcs12 -destkeystore /home/confluence/.keystore

/opt/jdk1.8.0_45/jre/bin/keytool -import -trustcacerts -alias root -file QuoVadis_Root_CA_2.crt -keystore /home/confluence/.keystore

/opt/jdk1.8.0_45/jre/bin/keytool -import -trustcacerts -alias intermediate -file QuoVadis_Intermediate_Global_SSL_ICA_G2.crt -keystore /home/confluence/.keystore

 

You listed the name extensions for each step!!!! Life saver!!! I am working on how to change the password needed to access the CSR or PFX as we try not to use this password on web servers. If I figure it out I will post a follow up with the notes.

Thank you Simon thank you!!!!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

78 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you