Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
79:upgrade_to_7_9_14 [2024/03/14 15:43] – [Upgrade to release 7.9.14.0 or higher] Weinlein, Thomas79:upgrade_to_7_9_14 [2025/03/12 13:50] (current) – [Stages server does not yet support HTTPS] Linz, Andreas
Line 2: Line 2:
  
 With this release we simplify the initial setup of Stages for production and follow a security by default approach. With this release we simplify the initial setup of Stages for production and follow a security by default approach.
-Therefore the default configuration for new Stages installations is prepared for **HTTPS only** access to Stages. For existing installations a few manual steps are neccessary as outlined below.+Therefore the default configuration for new Stages installations is prepared for **HTTPS only** access to Stages. For existing installation - after the upgrade to Stages 7.9.14.0 or higher - a few manual steps are necessary as outlined below.
  
-To be able to configure and use the latest TLS version 1.3 it is necessary to update the Java JDK 8 version on the server to **at least ''JDK-8u301''** or any higher 1.8.x version (64-Bit). Latest JDK 8 patch version is recommended.+To be able to configure and use the latest TLS version 1.3 it is necessary to update the Java JDK 8 version on the server to **at least ''JDK-8u381''** or any higher 1.8.x version (64-Bit). Latest JDK 8 patch version is recommended.
  
 The formerly error prone configuration for report execution and PDF printing is now also unified and delivered by default. The internal Stages communication will always use a separate connector on port ''8085'' that is not reachable from the outside. The formerly error prone configuration for report execution and PDF printing is now also unified and delivered by default. The internal Stages communication will always use a separate connector on port ''8085'' that is not reachable from the outside.
Line 53: Line 53:
  
 === Apply configuration changes === === Apply configuration changes ===
-[[configure_stages#apply-configuration-changes|Execute update and restart stages]]+Execute the configuration update and restart Stages as outlined [[configure_stages#apply-configuration-changes|here]]
  
 === Access Stages === === Access Stages ===
Line 67: Line 67:
 === Download self signed certificate === === Download self signed certificate ===
 Download the certificate keystore for the self signed certificate from here and store it in the ''$STAGES_CONF'' directory: Download the certificate keystore for the self signed certificate from here and store it in the ''$STAGES_CONF'' directory:
-https://download.methodpark.de/stages/stages-self-signed-cert/stages-self-signed-keystore.p12+https://download.stages.digital/stages/stages-self-signed-cert/stages-self-signed-keystore.p12
 Download the self signed certificate to be able to import it into your systems truststore. This is only useful for pure local access to Stages. Download the self signed certificate to be able to import it into your systems truststore. This is only useful for pure local access to Stages.
-https://download.methodpark.de/stages/stages-self-signed-cert/stages-self-signed.crt+https://download.stages.digitale/stages/stages-self-signed-cert/stages-self-signed.crt
  
  
Line 166: Line 166:
  
 === Apply configuration changes === === Apply configuration changes ===
-[[configure_stages#apply-configuration-changes|Execute update and restart stages]]+Execute configuration update and restart Stages as outlined [[configure_stages#apply-configuration-changes|here]]
  
 === Access Stages === === Access Stages ===
-Verify that Stages is available under ''%%https://stages.localhost%%'' or ''%%https://mystages.mycompany.com%%''. Please note that the browser will complain that the provided certificate is not valid or trusted. For the initial test please acknowledge the risk and click through to Stages.  +Verify that Stages is available under ''%%https://stages.localhost%%'' when you open the browser on the server machine or ''%%https://mystages.mycompany.com%%''. Please note that the browser will complain that the provided certificate is not valid or trusted. For the initial test please acknowledge the risk and click through to Stages.  
-After that you should [[configure_stages#configuring-tlsssl-certificate|create and configure your own singed certificate]] or create your own self signed certificate and import it into your browsers or systems truststore. +After that you should [[configure_stages#configuring-tlsssl-certificate|create and configure your own singed certificate]] or create your own self signed certificate and import it into your browsers or systems truststore. For pure local access to Stages you can import the default stages-self-signed.crt certificate as downloaded [[#Download self signed certificate|here]] into your browsers truststore.