Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 79:configure_stages [2024/03/07 16:24] – [Apply configuration changes] Weinlein, Thomas | 79:configure_stages [2024/03/08 10:32] (current) – Weinlein, Thomas | ||
|---|---|---|---|
| Line 42: | Line 42: | ||
| | '' | | '' | ||
| | Basic configuration ||| | | Basic configuration ||| | ||
| - | | '' | + | | '' |
| by using variable replacement | by using variable replacement | ||
| )) | | )) | | ||
| Line 63: | Line 63: | ||
| | '' | | '' | ||
| | '' | | '' | ||
| - | | [[#Configuring SSL Certificate|Certificates]] ||| | + | | [[#configuring-tlsssl-certificate|Certificates]] ||| |
| | '' | | '' | ||
| | [[kerberos_autologin|Kerberos SSO]] ||| | | [[kerberos_autologin|Kerberos SSO]] ||| | ||
| Line 120: | Line 120: | ||
| <code xml> | <code xml> | ||
| - | | + | < |
| - | < | + | < |
| - | [...] | + | [...] |
| - | </ | + | </ |
| </ | </ | ||
| Line 138: | Line 138: | ||
| <code xml> | <code xml> | ||
| < | < | ||
| - | < | + | |
| </ | </ | ||
| Line 147: | Line 147: | ||
| ==== Configuration of Stages Service Parameters ==== | ==== Configuration of Stages Service Parameters ==== | ||
| - | For configuring Stages service please proceed as follows: | + | For configuring Stages service please proceed as follows. In this example the max heap memory is changed. |
| * Windows: | * Windows: | ||
| Line 174: | Line 174: | ||
| The server.xml for new installations looks as follows: [[server.xml]] | The server.xml for new installations looks as follows: [[server.xml]] | ||
| - | Stages is started on TCP/IP port 80, 443 and 8085 and enforces usage of HTTPS by default. Thus, it can be accessed via the URL [[https://< | + | Stages is started on TCP/IP port 80, 443 and 8085 and enforces usage of HTTPS by default. Thus, it can be accessed via the URL [[https://< |
| When you try to access Stages via HTTP the client will be redirect to HTTPS instead. | When you try to access Stages via HTTP the client will be redirect to HTTPS instead. | ||
| Line 181: | Line 181: | ||
| <code xml> | <code xml> | ||
| - | | + | < |
| - | | + | |
| - | | + | protocol=" |
| - | | + | URIEncoding=" |
| - | | + | maxHttpHeaderSize=" |
| - | | + | maxThreads=" |
| - | | + | minSpareThreads=" |
| - | [...] | + | enableLookups=" |
| - | | + | [...] |
| + | </ | ||
| </ | </ | ||
| Line 195: | Line 196: | ||
| <code xml> | <code xml> | ||
| - | | + | < |
| - | | + | protocol=" |
| - | | + | URIEncoding=" |
| - | | + | maxHttpHeaderSize=" |
| - | | + | maxThreads=" |
| - | | + | minSpareThreads=" |
| - | | + | enableLookups=" |
| - | [...] | + | [...] |
| - | | + | </ |
| </ | </ | ||
| Line 211: | Line 212: | ||
| <code xml> | <code xml> | ||
| - | | + | < |
| - | | + | protocol=" |
| - | | + | proxyName=" |
| - | | + | proxyPort=" |
| - | | + | secure=" |
| - | | + | scheme=" |
| - | | + | URIEncoding=" |
| - | | + | maxHttpHeaderSize=" |
| - | | + | maxThreads=" |
| - | | + | minSpareThreads=" |
| - | | + | enableLookups=" |
| - | | + | acceptCount=" |
| - | | + | connectionTimeout=" |
| - | | + | disableUploadTimeout=" |
| - | | + | address=" |
| - | /> | + | /> |
| </ | </ | ||
| Line 236: | Line 237: | ||
| In case you use a IPv6 only configuration please replace '' | In case you use a IPv6 only configuration please replace '' | ||
| - | ==== Configuring SSL Certificate ==== | + | Further explanations of the connector attributes are available at [[https:// |
| + | |||
| + | ==== Configuring | ||
| Stages comes with a self signed certificate for [[https:// | Stages comes with a self signed certificate for [[https:// | ||
| - | Please store your PKCS #12 keystore file in '' | + | * Register a DNS alias for the server, e.g. “stages.company.com” |
| + | * Apply for a TLS/SSL certificate for the server which refers to the above alias. Depending on your local procedures, this might require creating a certificate request (e.g. see https:// | ||
| + | * Store your PKCS# | ||
| '' | '' | ||
| Line 252: | Line 257: | ||
| </ | </ | ||
| - | For more details on certificate generation please refer to [[certificate_generation]]. | + | [[# |
| ==== Configuration for usage with Reverse Proxy ==== | ==== Configuration for usage with Reverse Proxy ==== | ||
| - | in case you want to terminate the SSL connection on a reverse proxy, you need to adapt the '' | + | in case you want to terminate the TSL connection on a reverse proxy ([[https:// |
| E.g. | E.g. | ||
| Line 274: | Line 278: | ||
| | | ||
| | | ||
| - | proxyname=" | + | proxyName=" |
| - | proxyport=" | + | proxyPort=" |
| | | ||
| > | > | ||
| Line 327: | Line 331: | ||
| set JAVA_OPTS=[...] -Djavax.net.ssl.trustStoreType=Windows-ROOT -Djavax.net.ssl.trustStore=NUL | set JAVA_OPTS=[...] -Djavax.net.ssl.trustStoreType=Windows-ROOT -Djavax.net.ssl.trustStore=NUL | ||
| </ | </ | ||
| - | This is the default for new installations of 7.9.14.0 | + | This is the default for new installations of Stages |
| Linux: | Linux: | ||
| Line 336: | Line 340: | ||
| ===== Licenses ===== | ===== Licenses ===== | ||
| - | Stages is delivered with a temporary license that allows running Stages on any machine. Running Stages with a permanent license requires the Stages server machine to have a fixed IP address. To request a permanent license for running Stages on a specific server, please follow these steps: | + | Stages is delivered with a temporary license that allows running Stages on any machine. Running Stages with a permanent license requires the Stages server machine to have a fixed IP address. To request a permanent license for running Stages on a specific server, please follow these steps: |
| + | |||
| + | * Install Stages on the server | ||
| + | | ||
| + | | ||
| + | | ||
| + | * An email with all the necessary information will be opening | ||
| + | * Send the email to the Stages Customer Care team | ||
| ===== Local Message Customization ===== | ===== Local Message Customization ===== | ||