On 04/06/14 07:44, Luis Cañas-Díaz wrote: > On 03/06/14 15:33, MANUEL ESCRICHE VICENTE wrote: >> Luis, te envío respuesta de Atlassian. > > Recibido Manuel. Voy a ver pues como se hace esto con Tomcat pues. Si > bien lo que dice de incluir la clave privada con el certificado en el > mismo fichero no tiene lógica alguna. Sería como dejar siempre las > llaves puestas por fuera en casa para implementar un "bombín". > > Durante el día de hoy te comento. Ya he dado con el problema Manuel. Debo convertir los certificados al format extraño que usa Tomcat. Vaya cosas que se aprenden ;) Voy a ello! > > Saludos, > Luis. > >> >> *From:*Daniel Leng [Atlassian] [mailto:jira-support-system at atlassian.com] >> *Sent:* martes, 03 de junio de 2014 15:19 >> *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 3:18 PM >> >> Hi Manuel, >> >> Hmm, as far as I remember the certificate should already include the >> private key. Our documentation is a generic tutorial on importing SSL >> certificates into a Tomcat server, but the instructions may vary >> depending on the certificate vendor. You may want to check with your >> certificate vendor on the certificate format that is provided. >> Also, it seems that you have linked an older version of the >> documentation, as you are on JIRA 6.x you should follow this one: >> https://confluence.atlassian.com/display/JIRA061/Running+JIRA+over+SSL+or+HTTPS >> >> >> Best regards, >> Daniel >> >> Status changed to *Waiting For Customer* >> >> Today 3:18 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:07 PM >> >> >> 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 > > -- Luis Cañas-Díaz lcanas at bitergia.com - Software Engineer http://www.bitergia.com "Software metrics for your peace of mind"
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy