We have an internal Stash and JIRA environment working great. We decided that we want to have both these to be delivered over SSL utilizing a self-signed cert. So as I have looked at it, I see that the process to do both of these is slightly different. I'd prefer the process to be similar for maintenance. Documented Stash Process In A Nutshell * $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keystore /conf/stash.jks * Edit /conf/server.xml and add: /conf/stash.jks" /> * Comment out port 7990 config * Restart Stash I'd prefer the process be more like the JIRA documentation to wit. Can I make the generated key alias stash? then add something like the JIRA connector config parameters modified below? keystoreFile=" /conf/stash.jks" keyAlias="stash" keystorePass="changeit" keystoreType="JKS"

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

stash over ssl

pnelsonsr

We have an internal Stash and JIRA environment working great. We decided that we want to have both these to be delivered over SSL utilizing a self-signed cert. So as I have looked at it, I see that the process to do both of these is slightly different. I'd prefer the process to be similar for maintenance.

Documented Stash Process In A Nutshell

$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keystore <stash-home>/conf/stash.jks
Edit <stash-home>/conf/server.xml and add:
<Connector port="8443"
 maxHttpHeaderSize="8192"
  SSLEnabled="true"
  maxThreads="150"
  minSpareThreads="25"
  maxSpareThreads="75"
  enableLookups="false"
  disableUploadTimeout="true"
  useBodyEncodingForURI="true"
  acceptCount="100"
  scheme="https"
  secure="true"
  clientAuth="false"
  sslProtocol="TLS"
  keystoreFile="<stash-home>/conf/stash.jks" />
Comment out port 7990 config
Restart Stash

I'd prefer the process be more like the JIRA documentation to wit. Can I make the generated key alias stash? then add something like the JIRA connector config parameters modified below?

keystoreFile="<stash-home>/conf/stash.jks"
keyAlias="stash"
keystorePass="changeit"
keystoreType="JKS"

Accepted answers

gustavo_refosco

Hi Patrick,

Despite the docs may be slightly different you can perfectly use the options you are mentioning - consider that Stash, as JIRA, runs over a Tomcat platform, so these options are common to the Tomcat connector.

Regards,

Gustavo Refosco

All comments

gustavo_refosco

Hi Patrick,

Regards,

Gustavo Refosco

pnelsonsr

Great I'm going to work out the processes and try to implement within the next few days. I'll ping back here with the results!

pnelsonsr

Does setting up ssl only on Stash and JIRA have any effect on the application connection between Stash and JIRA?

gustavo_refosco

Hi Patrick, If the Application Link is already created, it must be re-created, using the new Base URLs of both apps. You also need to make sure they'll be able to communicate via SSL, so the proper certificates need to be imported into the truststore used by each app. Regards, Gustavo Refosco

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bitbucket-administration