-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We have a new JIRA release quite regularly. Also, we encourage users to stay up to date with the used JIRA version.
Taking the above into account users may find themselves in a need of migrating SSL keys between their systems rather often. Moreover, it can cause someone system to become inaccessible, if on upgrade the SSL migration step isn't performed.
It seems unnecessary and could be easily avoided by allowing users to retain their currently used JVM. Alternatively, we could consider importing the 'old' JIRA's keystore to the one provided with the installer.
- relates to
-
JRACLOUD-25475 Installer (specifically its upgrade feature) should import SSL KeyStore or allow reuse of a custom, existing JVM
- Closed
[JRASERVER-25475] Installer (specifically its upgrade feature) should import SSL KeyStore or allow reuse of a custom, existing JVM
Workflow | Original: JAC Suggestion Workflow [ 3052038 ] | New: JAC Suggestion Workflow 3 [ 3678437 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2614766 ] | New: JAC Suggestion Workflow [ 3052038 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2579163 ] | New: Confluence Workflow - Public Facing v4 [ 2614766 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358177 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2579163 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2125574 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358177 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088052 ] | New: JIRA Bug Workflow w Kanban v6 [ 2125574 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 878050 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088052 ] |
Description |
Original:
We have a new JIRA release quite regularly. Also, we encourage users to stay up to date with the used JIRA version.
Taking the above into account users may find themselves in a need of migrating SSL keys between their systems rather often. Moreover, it can cause someone system to become inaccessible, if on upgrade the SSL migration step isn't performed. It seems unnecessary and could be easily avoided by allowing users to retain their currently used JVM. Alternatively, we could consider importing the 'old' JIRA's keystore to the one provided with the installer. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-25475]. {panel} We have a new JIRA release quite regularly. Also, we encourage users to stay up to date with the used JIRA version. Taking the above into account users may find themselves in a need of migrating SSL keys between their systems rather often. Moreover, it can cause someone system to become inaccessible, if on upgrade the SSL migration step isn't performed. It seems unnecessary and could be easily avoided by allowing users to retain their currently used JVM. Alternatively, we could consider importing the 'old' JIRA's keystore to the one provided with the installer. |
Link |
New:
This issue relates to |
Labels | New: affects-server |