Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
We are trying to configure SSL for Bitbucket 5.6.1 using the guide at this link and are having some issues.
We have been granted a cert from our network security team using our internal CA Root. I am generating the ssl-keystore file by running the following command-
keytool -import -alias tomcat -file CARootFile.crt -keystore ./ssl-keystore -storepass changeit
I have then added the following lines to the bitbucket.properties file-
Post service bounce, I receive the attached log output. A notable log entry is-
java.lang.IllegalArgumentException: java.io.IOException: Alias name [tomcat] does not identify a key entry
Interesting thing is when I execute the following-
keytool -list -keystore ./ssl-keystore -storepass changeit
I receive the following-
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
tomcat, Jan 14, 2018, trustedCertEntry,
Certificate fingerprint (SHA1): 92:C5:8A:CC:54:50:42:03:48:9A:3C:60:9C:49:60:53:96:2C:CB:22
Any assistance / guidance would be appreciated. Thanks in advance!
Could you take a look at the resource below?
As mentioned there, this message refers to an error on the alias name. Try to follow the steps mentioned there in order to set the alias correctly.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs