Changes for page 3. Advanced Configurations
Last modified by teamwire001 on 2025/09/11 14:58
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,86 +1,48 @@ 1 - {{id name="4-hostname"/}}1 +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.Profile-and-Settings.WebHome||anchor="04-advanced"]]. 2 2 3 -= Server = 4 4 5 -{{ tabsidsToLabels="server1=Desktop 4,server2=Until Desktop 3.4.3"/}}4 +{{id name="hostname"/}} 6 6 7 -(% id="server1" %) 8 -((( 9 -{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. 6 += Backend hostname = 10 10 8 +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. 11 11 12 -If required,please enter the custom**servername** here. Youmustnotenter theprotocol or path but thenameonly.It is recommendedtoadd thisinformation in ordertospeedup theprocess andpreventregistration failures.10 +If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}. 13 13 14 -If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##. 15 -))) 16 16 17 -(% id="server2" %) 18 -((( 19 -{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]], and in the app's [[Settings ~> Advanced options>>doc:Public.Applications.Desktop.User-Manual.Profile-and-Settings.WebHome||anchor="04-advanced"]] when you are logged in. 13 +{{id name="proxy"/}} 20 20 21 - 22 -If required, please enter the custom **backend hostname** 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. 23 - 24 -If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##. 25 -))) 26 - 27 - 28 -{{id name="4-proxyurl"/}} 29 - 30 30 = Proxy server = 31 31 32 -{{tabs idsToLabels="proxy1=Desktop 4, proxy2=Until Desktop 3.4.3"/}} 33 - 34 -(% id="proxy1" %) 35 -((( 36 -{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. 37 - 38 - 39 39 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.** 40 40 41 -Please enter the complete URL incl. protocol (e.g. ##http## or ##https##) and port. The different types of proxy and their syntaxes are explained down below. 42 42 43 - For the followingexample we assume the proxy is running onahost named ##your-proxy.com## with port 9000. If yourproxy needs basic HTTPS authentication, the credentials can be included in the URL as shown.20 +{{id name="proxyurl"/}} 44 44 45 -* **HTTPS Proxy** 46 -##https:~/~/your-proxy.com:9000## 47 -##https:~/~/username:password@your-proxy.com:9000## 22 +== Apply proxy URL == 48 48 49 -* **PAC Proxy** 50 -##pac+http:~/~/file-provider.com/proxy.pac## 51 -))) 24 +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. 52 52 53 -(% id="proxy2" %) 54 -((( 55 -{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]], and in the app's [[Settings ~> Advanced options>>doc:Public.Applications.Desktop.User-Manual.Profile-and-Settings.WebHome||anchor="04-advanced"]] when you are logged in. 56 - 57 - 58 -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.** 59 - 60 -Please enter the complete URL incl. protocol (e.g. ##http## or ##https##) and port. The different types of proxy and their syntaxes are explained down below. 61 - 62 -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 or SOCKS-5 authentication, the credentials can be included in the URL as shown. 63 - 64 64 * **HTTPS Proxy** 65 - ##https:~/~/your-proxy.com:9000##66 - ##https:~/~/username:password@your-proxy.com:9000##27 +{{code language="html"}}https://your-proxy.com:9000{{/code}} 28 +{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}} 67 67 68 68 * **SOCKS-5 Proxy** 69 - ##socks5:~/~/your-proxy.com:9000##70 - ##socks5:~/~/username:password@your-proxy.com:9000##31 +{{code language="html"}}socks5://your-proxy.com:9000{{/code}} 32 +{{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}} 71 71 72 72 * **SOCKS-4 Proxy** 73 - ##socks4:~/~/your-proxy.com:9000##35 +{{code language="html"}}socks4://your-proxy.com:9000{{/code}} 74 74 75 75 * **PAC Proxy** 76 - ##pac+http:~/~/file-provider.com/proxy.pac##38 +{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}} 77 77 ## ## 78 78 79 -(% class="box-title" %) 80 -System Proxy 41 +{{id name="systemproxy"/}} 81 81 43 +== Use system proxy == 44 + 82 82 If the proxy data are already provided to the (Windows) system, you can select **Use system proxy** to apply the operating system's internet settings. 83 -))) 84 84 85 85 86 86 {{id name="certificate"/}} ... ... @@ -87,41 +87,27 @@ 87 87 88 88 = Server certificate = 89 89 90 -{{tabs idsToLabels="certificate1=Desktop 4, certificate2=Until Desktop 3.4.3"/}} 91 - 92 -(% id="certificate1" %) 93 -((( 94 -Custom server certificates are currently not supported by Desktop version 4. 95 -))) 96 - 97 -(% id="certificate2" %) 98 -((( 99 -{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]]. 100 - 101 - 102 102 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. 103 103 104 104 105 105 {{id name="customcertificatefile"/}} 106 106 107 -(% class="box-title" %) 108 -Use a custom certificate file 57 +== Choose custom certificate file == 109 109 110 110 Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer. 111 111 112 -{{info}} 113 -Please make sure to use the unix line feed ##LF## on your certificate. Any other control characters like ##CR## or Windows' ##CR LF## will not be valid. 61 +(% class="box infomessage" %) 62 +((( 63 +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. 114 114 115 115 Also note, that the path used to refer to your certificate must not contain any spaces. 116 - {{/info}}66 +))) 117 117 118 118 119 119 {{id name="systemcertificatechain"/}} 120 120 121 -(% class="box-title" %) 122 -Use system certificate chain (Windows) 71 +== Use system certificate chain (Windows) == 123 123 124 124 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. 125 -))) 126 126 127 127 ## ##