Changes for page 3. Advanced Configurations

Last modified by teamwire001 on 2025/09/11 14:58

From 2.1 to 1.4

From version 4.2

edited by teamwire001
on 2025/09/11 14:58

Change comment: DOC-434

To version 2.1

edited by teamwire003
on 2023/11/07 14:34

Change comment: DOC-247

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.teamwire001
++XWiki.teamwire003

Content

@@ -1,136 +1,112 @@
++= Desktop 4.0.0 or newer =
++
++These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
++
++
  {{id name="4-hostname"/}}
--= Server =
++== Server ==
--{{tabs idsToLabels="server1=Desktop 4, server2=Until Desktop 3.4.3"/}}
++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.
--(% id="server1" %)
--(((
--{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
++If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
--If required, please enter the custom **server name** 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.
++{{id name="4-proxyurl"/}}
--If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##.
--)))
++== Proxy URL ==
--(% id="server2" %)
--(((
--{{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.
++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.**
--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.
++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 authentication, the credentials can be included in the URL as shown.
--If your organisation is using the Teamwire Cloud Backend, please enter ##backend.teamwire.eu##.
--)))
++* **HTTPS Proxy**
++{{code language="html"}}https://your-proxy.com:9000{{/code}}
++{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
--(% style="border-color:var(--gili_blue_300)" %)
++* **PAC Proxy**
++{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
++## ##
++
  ----
++{{id name="desktop-previous"/}}
--{{id name="4-proxyurl"/}}
++= Until Desktop 3.4.2 =
--= Proxy server =
++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"]].
--{{tabs idsToLabels="proxy1=Desktop 4, proxy2=Until Desktop 3.4.3"/}}
--(% id="proxy1" %)
--(((
--{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
++{{id name="hostname"/}}
++== Backend hostname ==
--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.**
++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.
--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.
++If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
--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.
--* **HTTPS Proxy**
--##https:~/~/your-proxy.com:9000##
--##https:~/~/username:password@your-proxy.com:9000##
++{{id name="proxy"/}}
--* **PAC Proxy**
--##pac+http:~/~/file-provider.com/proxy.pac##
--)))
++== Proxy server ==
--(% id="proxy2" %)
--(((
--{{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.
++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.**
--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.**
++{{id name="proxyurl"/}}
--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.
++=== Apply proxy URL ===
--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.
++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.
  * **HTTPS Proxy**
--##https:~/~/your-proxy.com:9000##
--##https:~/~/username:password@your-proxy.com:9000##
++{{code language="html"}}https://your-proxy.com:9000{{/code}}
++{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
  * **SOCKS-5 Proxy**
--##socks5:~/~/your-proxy.com:9000##
--##socks5:~/~/username:password@your-proxy.com:9000##
++{{code language="html"}}socks5://your-proxy.com:9000{{/code}}
++{{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}}
  * **SOCKS-4 Proxy**
--##socks4:~/~/your-proxy.com:9000##
++{{code language="html"}}socks4://your-proxy.com:9000{{/code}}
  * **PAC Proxy**
--##pac+http:~/~/file-provider.com/proxy.pac##
++{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
  ## ##
--(% class="box-title" %)
--System Proxy
++{{id name="systemproxy"/}}
++=== Use system proxy ===
++
  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.
--)))
--(% style="border-color:var(--gili_blue_300)" %)
------
--
  {{id name="certificate"/}}
--= Server certificate =
++== Server certificate ==
--{{tabs idsToLabels="certificate1=Desktop 4, certificate2=Until Desktop 3.4.3"/}}
--
--(% id="certificate1" %)
--(((
--Custom server certificates are currently not supported by Desktop version 4.
--)))
--
--(% id="certificate2" %)
--(((
--{{icon name="cog"/}} These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
--
--
  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.
  {{id name="customcertificatefile"/}}
--(% class="box-title" %)
--Use a custom certificate file
++=== Choose custom certificate file ===
  Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
--{{info}}
--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.
++(% class="box infomessage" %)
++(((
++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.
  Also note, that the path used to refer to your certificate must not contain any spaces.
--{{/info}}
++)))
  {{id name="systemcertificatechain"/}}
--(% class="box-title" %)
--Use system certificate chain (Windows)
++== Use system certificate chain (Windows) ==
  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.
--)))
--(% style="border-color:var(--gili_blue_300)" %)
------
--
  ## ##

Changes for page 3. Advanced Configurations

Summary

Details

Last edited

Content