[Fiware-support] FW: [SUPPORT] [JIRA Support] How to import the private/secret key when running JIRA over HTTPS

[MANUEL ESCRICHE VICENTE]

Gracias.
Atlassian, ha movido el ticket que pusimos a Resolved, y lo ha cerrado.

-----Original Message-----
From: Luis Cañas-Díaz [mailto:lcanas at bitergia.com]
Sent: martes, 24 de junio de 2014 17:54
To: MANUEL ESCRICHE VICENTE
Cc: fiware-support
Subject: Re: FW: [SUPPORT] [JIRA Support] How to import the private/secret key when running JIRA over HTTPS

On 18/06/14 08:41, MANUEL ESCRICHE VICENTE wrote:
> ¿Algún progreso?

Estoy ahora con esto probando en una máquina de prueba. En cuanto lo pruebe lo aplico (espero que esta tarde/noche)

Saludos,
Luis.
>
> Atlassian cierra el ticket ante nuestra falta de actividad.
>
> *From:*Atlassian Support [mailto:jira-support-system at atlassian.com]
> *Sent:* martes, 17 de junio de 2014 17:12
> *To:* MANUEL ESCRICHE VICENTE
> *Subject:* [SUPPORT] [JIRA Support] How to import the private/secret
> key when running JIRA over HTTPS
>
> New comment for the request "How to import the private/secret key when
> running JIRA over HTTPS" with key JSP-194612 has been added...
>
> *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>
>   Inactive - Pending Closure
>
>
>         Atlassian Support
>
> Today 5:11 PM
>
> Dear Manuel Escriche,
>
> We have noticed that this issue has not been updated for a period of 5
> business days.
> We will assume that this issue is resolved and close the ticket. If
> you still need help, just reply to this email or comment on the case
> via the web and we will reopen the case. You can also request a delay
> (freeze) now if you need more time to respond.
> If you've managed to resolve this issue locally, please take a moment
> to share your solution for future reference.
>
> Kind Regards,
> The Atlassian JIRA Support Team
>
> You can view the full request
> <https://support.atlassian.com/servicedesk/customer/jsp/configuration-
> query-194612>
>
>
>     Previous activity
>
> Status changed to *Inactive - Pending Closure*
>
> Today 5:11 PM
>
> Status changed to *Waiting For Customer*
>
> 10/Jun/14 4:49 PM
>
>
>         Daniel Leng [Atlassian]
>
> 10/Jun/14 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+SS
> L+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
>
> 5 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+SS
> L+or+HTTPS#RunningJIRAoverSSLorHTTPS-ImportCertificateintotheTrust-sto
> re) , 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 y sus adjuntos se dirigen exclusivamente a su
> destinatario, puede contener información privilegiada o confidencial y
> es para uso exclusivo de la persona o entidad de destino. Si no es
> usted. el destinatario indicado, queda notificado de que la lectura,
> utilización, divulgación y/o copia sin autorización puede estar
> prohibida en virtud de la legislación vigente. Si ha recibido este
> mensaje por error, le rogamos que nos lo comunique inmediatamente por
> esta misma vía y proceda a su destrucción.
>
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual
> or entity named above. If the reader of this message is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited.
> If you have received this transmission in error, do not read it.
> Please immediately reply to the sender that you have received this
> communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é
> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> senhoria o destinatário indicado, fica notificado de que a leitura,
> utilização, divulgação e/ou cópia sem autorização pode estar proibida
> em virtude da legislação vigente. Se recebeu esta mensagem por erro,
> rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> proceda a sua destruição


--
Luis Cañas-Díaz
lcanas at bitergia.com - Software Engineer
http://www.bitergia.com
"Software metrics for your peace of mind"

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição