Luis, algún progreso? Gracias. Manuel From: MANUEL ESCRICHE VICENTE Sent: miércoles, 11 de junio de 2014 9:38 To: 'Luis Cañas-Díaz' Subject: FW: [SUPPORT] [JIRA Support] How to import the private/secret key when running JIRA over HTTPS From: Daniel Leng [Atlassian] [mailto:jira-support-system at atlassian.com] Sent: martes, 10 de junio de 2014 16:49 To: MANUEL ESCRICHE VICENTE Subject: [SUPPORT] [JIRA Support] How to import the private/secret key when running JIRA over HTTPS Status of the request "How to import the private/secret key when running JIRA over HTTPS" with key JSP-194612 has been changed... JIRA Support - Configuration Query<https://support.atlassian.com/servicedesk/customer/jsp> Reference: JSP-194612<https://support.atlassian.com/servicedesk/customer/jsp/configuration-query-194612> How to import the private/secret key when running JIRA over HTTPS<https://support.atlassian.com/servicedesk/customer/jsp/configuration-query-194612> Waiting For Customer Daniel Leng [Atlassian] Today 4:49 PM Hi Manuel, In that case I recommend using Portecle as per our SSL docs<https://confluence.atlassian.com/display/JIRA061/Running+JIRA+over+SSL+or+HTTPS> as a visual tool for performing the import, instead of using command prompt. You can use portecle to open an existing keystore (File >> Open keystore file...), look for the keystore that is used by the JAVA installation that JIRA is using. Once opened, you can simply import your .pem certificate into the keystore (Tools >> Import Trusted Certificate), and then remember to Save the keystore. This should work, but you need to make sure of the following points: 1. Ensure that you know which JAVA installation that JIRA is using. (Log in to your JIRA system, go to Administration >> System >> System Info), look for the line titled java.home. This is the JAVA installation that your JIRA is using) 2. The keystore that your JAVA installation uses, by default, is $JAVA_INSTALLATION/jre/lib/security/cacerts Do remember to restart JIRA after you have imported the .pem file and saved the keystore. I don't think you need to worry about separate private keys and certificates, as the .pem file should be enough. Let me know if this helps! Best regards, Daniel Status changed to Waiting For Customer Today 4:49 PM You can view the full request<https://support.atlassian.com/servicedesk/customer/jsp/configuration-query-194612> Previous activity Status changed to Atlassian Investigating Today 3:34 PM Manuel Escriche Today 3:34 PM Hi Daniel, Thanks for the link. We read it all again and tried to follow the process. However, we aren't done yet since we found some difficulty we don't know how to overcome. I mean "we have a signed certificate in PEM format. We would like to know how to import both the private key and the signed certificate using that format and using the command line tool." Thanks in advance! Kind regards, Manuel Status changed to Waiting For Customer 03/Jun/14 3:18 PM 2 older messages<https://support.atlassian.com/servicedesk/customer/jsp/configuration-query-194612> Details Priority Level 4 Affects Version/s 6.1.7 Description According to the following tip (https://confluence.atlassian.com/display/JIRA051/Running+JIRA+over+SSL+or+HTTPS#RunningJIRAoverSSLorHTTPS-ImportCertificateintotheTrust-store) , it is possible to import the certificate to run JIRA over HTTPS. But I miss how to import the private/secret key. Would you please explain? Customer Timezone GMT+1 This message is automatically generated by JIRA Service Desk. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA Service Desk, see: http://www.atlassian.com/software/jira/service-desk ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-support/attachments/20140613/1c0e4b3c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy