Two questions about the 'SSL Truststore' configuration setting.
Asked by Etan Reisner:

The FishEye documentation seems to indicate that the 'SSL Truststore' setting is optional however I cannot seem to hit the 'Update' button with that field (and the associated password fields) empty as I get an 'the ssl truststore password seems to be incorrect - it was unable to open the truststore file' error when I try.

My question is do other people see this or has something gone wrong on my end? (I'm using FishEye 2.10.2 for the record.)

My main question, however, is has anyone gotten the 'SSL Truststore' to work correctly? I am using an SSL certificate signed by an intermediate CA that is itself signed by a CA that is in the default java cacerts keystore. I therefore assumed that to complete the cert chain I needed to add the intermediate certificate to the truststore. So I did that (both in the same truststore that contains my private key and in a new truststore with only that one certificate) but could not get Jira auth or an applink to Jira to work correctly. (I also tried importing both the intermediate and root CA certificates into a new keystore, assuming that the note about alternative keystore locations applies to the 'SSL Truststore' setting as well as to -Djavax.net.ssl.trustStore but that did not work either. I should also add that from some testing with the SSLPoke java class it would appear that that note is, in fact, incorrect and java does load that keystore and the system keystore but that's an issue for another time.)

As a last test I added the intermediate certificate to the default cacerts keystore and the connection worked immediately. (I did not try specifying -Djavax.net.ssl.trustStore on the FishEye command line via FISHEYE_OPTS though I have considered going back and trying that to see if it works.)

Was I doing something wrong this whole time? Was I not understanding the purpose of the 'SSL Truststore' option? Is something broken about this setting? Any help/comments would be appreciated.

References:

<https://confluence.atlassian.com/display/FISHEYE/FishEye+SSL+configuration>

<https://confluence.atlassian.com/display/JIRA/Connecting+to+SSL+services>


Answers:
author: Peppo Herney
body: Hello Etan,

I don't think you did anything worng.

SSL works in our Installation now. <https://confluence.atlassian.com/display/FISHEYE/FishEye+SSL+configuration> helped.

The admin web interface did not work for me nether. I received the same error message 'the ssl truststore password seems to be incorrect - it was unable to open the truststore file'. Even when pointing to an inexistent file. This seems to be broken!

Finally I pasted

\<ssl bind=":443" keystore="D:\\Atlassian\\Data\\fecru\\keystore.kst" keystore-password="pass..." truststore="D:\\Atlassian\\Data\\fecru\\keystore.kst" truststore-password="pass..."/\>

inside the \<web-server\> tag of the config.xml, restarted Fisheye and it worked.


author: Ihar Kudrautsau
body: Hi,

I can answer first question only: you just have to fill truststore fields exactly as keystore fields.

comments: author: Etan Reisner
body: I don't understand your answer at all. I believe I know what I'm supposed to be putting in those fields and I believe I have done so correctly (in more than one way). The issue is that the fields appear not to work for what I believe they are supposed to do.


Tags: ssl