Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Fisheye with PKCS12 directly utilized

Mike Rathwell Community Leader Aug 31, 2015

I currently have Confluence, JIRA, Crowd, and Bamboo configured to use the PKCS12 for SSL directly.

I am trying to find out if I can do the same with Fisheye. All I can see are the common commands to generate the various certificate types typically used by Java that are in the other configuration documents. In interest of consistency in my environment is there a way to configure Fisheye with the equivalent Tomcat keystoreType=PKCS12 switch?

1 answer

0 votes

See this page, it explains how to use PKCS12 certificates with FishEye. Kind regards, Piotr

Mike Rathwell Community Leader Sep 01, 2015

Piotr, I did see that page... It doesn't do what I was looking for (and the Atlassian Answers site told me I had blacklisted words when I tried to explain it more fully). In my JIRA, Bamboo, and Confluence instances, I use the PKCS12 DIRECTLY. I can set the keystoreType in the server.xml config file and just point at it without extracting the other variants of the certificate to use in traditional java keystore mode. What i was looking for was how to do that...

Mike Rathwell Community Leader Sep 01, 2015

Adding to my comment... What I'd be looking for is what is described in the server.xml for my Confluence, JIRA, Bamboo, and Crowd instances... The Connector statement is in the following form: <Connector port="443" maxHttpHeaderSize="8192" maxThreads="300" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" SSLEnabled="true" keystoreFile="<filesystempath>\corpWildcardwithChain.pfx" keystorePass="password" keystoreType="PKCS12"/>

Mike, Thanks for clarification. At the moment the only keystore format supported by FishEye/Crucible is JKS. I can see Jetty (embedded in FishEye/Crucible) supports PKCS12 keystores, so seems like there are no reasons to not consider such improvement. Would you consider raising a public issue in project and vote on it, please? Kind regards, Piotr

Suggest an answer

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

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

107 views 2 9
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