Changes for page 3. Advanced Configurations
Last modified by teamwire001 on 2026/07/08 06:30
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 3. Advanced Configurations1 +h. Advanced Configurations - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Public.Applications.Desktop.WebHome 1 +Public.Applications.Desktop.User-Manual.WebHome - Content
-
... ... @@ -1,40 +1,79 @@ 1 -{{id name="4-hostname"/}} 1 +(% class="box" %) 2 +((( 3 +These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]] or later by opening the app's [[Settings > Advanced options>>doc:Public.Applications.Desktop.User-Manual.Settings.WebHome||anchor="HAdvanced"]]. 4 +))) 2 2 3 -= Server = 4 4 5 -{{i conname="cog"/}} These settings are accessible during the [[Login and Registrationprocess>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].7 +{{id name="hostname"/}} 6 6 9 += Backend Hostname = 7 7 8 -If required, please enter the custom **servername**here. You must not enter the protocol or path but the name only. It is recommended to add this information in order to speed up the process and prevent registration failures.11 +If required, please enter the custom backend hostname here. You **must not** enter the protocol or path but the hostname only. It is recommended to add this information in order to speed up the process and prevent registration failures. 9 9 10 -If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##.13 +If your organisation is using the Teamwire Public Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}. 11 11 12 12 13 -{{id name=" 4-proxyurl"/}}16 +{{id name="proxy"/}} 14 14 15 -= Proxy server =18 += Proxy Server = 16 16 17 - {{iconname="cog"/}} Thesesettingsareaccessibleduringthe[[LoginandRegistration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].20 +In order to work properly with a proxy server, Teamwire needs your proxy to support the **HTTP CONNECT method,** the **HTTP Upgrade mechanism** and has to allow all **Sec-Websocket-* headers.** 18 18 19 19 20 - In orderto work properly withaproxy server, Teamwireneeds yourproxyto support the **HTTP CONNECT method,** the **HTTP Upgrade mechanism** and has to allow all **Sec-Websocket-* headers.**23 +{{id name="proxyurl"/}} 21 21 22 - Pleaseenter the complete URL incl.protocol(e.g. ##http## or ##https##) and port. The different typesof proxyandtheir syntaxes are explained down below.25 +== Apply Proxy URL == 23 23 24 -For the following example we assume the proxy is running on a host named ##your-proxy.com##with port 9000. If your proxy needs basic HTTPS authentication, the credentials can be included in the URL as shown.27 +Please enter the complete URL incl. protocol (e.g. {{code}}http{{/code}} or {{code}}https{{/code}}) and port. The different types of proxy and their syntaxes are explained down below. For the following example we assume the proxy is running on a host named {{code}}your-proxy.com{{/code}} with port {{code}}9000{{/code}}. If your proxy needs basic HTTPS or SOCKS-5 authentication, the credentials can be included in the URL as shown. 25 25 26 26 * **HTTPS Proxy** 27 - ##https:~/~/your-proxy.com:9000##28 - ##https:~/~/username:password@your-proxy.com:9000##30 +{{code language="html"}}https://your-proxy.com:9000{{/code}} 31 +{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}} 29 29 33 +* **SOCKS-5 Proxy** 34 +{{code language="html"}}socks5://your-proxy.com:9000{{/code}} 35 +{{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}} 36 + 37 +* **SOCKS-4 Proxy** 38 +{{code language="html"}}socks4://your-proxy.com:9000{{/code}} 39 + 30 30 * **PAC Proxy** 31 -##pac+http:~/~/file-provider.com/proxy.pac## 41 +{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}} 42 + 32 32 ## ## 33 33 45 +{{id name="systemproxy"/}} 46 + 47 +== Use System Proxy == 48 + 49 +If the proxy data are already provided to the (Windows) system, you can select **Use system proxy** to apply the OS' internet settings. 50 + 51 + 34 34 {{id name="certificate"/}} 35 35 36 -= Server certificate =54 += Server Certificate = 37 37 38 - Customserver certificates arecurrently notsupported.56 +If the backend server uses a self-signed certificate or if it is signed by a Certificate Authority (CA), that is not well known, you will have to provide the certificate chain. 39 39 58 + 59 +{{id name="customcertificatefile"/}} 60 + 61 +== Choose Custom Certificate File == 62 + 63 +Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer. 64 + 65 +(% class="box infomessage" %) 66 +((( 67 +Please make sure to use the unix line feed {{code}}LF{{/code}} on your certificate. Any other control characters like ##CR## or Windows' ##CR LF## will not be valid. 68 + 69 +Also note, that the path used to refer to your certificate must not contain any spaces. 70 +))) 71 + 72 + 73 +{{id name="systemcertificatechain"/}} 74 + 75 +== Use System Certificate Chain (Windows) == 76 + 77 +Select this option if the custom certificate has been applied to the Microsoft Management Console. Teamwire will automatically check the so-called Certificate Trust Store for any necessary information. 78 + 40 40 ## ##