Skip to Content
Last modified by teamwire001 on 2024/12/12 14:41
From version 1.2
edited by teamwire001
on 2021/12/06 07:58
Change comment: api 16 documenation
To version 3.1
edited by teamwire001
on 2024/12/12 14:41
Change comment: DOC-390 + heading hierarchy fixes

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -f. Advanced Configurations
1 +3. Advanced Configurations
Parent
... ... @@ -1,1 +1,1 @@
1 -Public.Applications.Desktop.User-Manual.WebHome
1 +Public.Applications.Desktop.WebHome
Content
... ... @@ -1,9 +1,46 @@
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"]].
1 += Desktop 4.0.0 or newer =
2 2  
3 +These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
3 3  
5 +
6 +{{id name="4-hostname"/}}
7 +
8 +== Server ==
9 +
10 +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 +
12 +If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
13 +
14 +
15 +{{id name="4-proxyurl"/}}
16 +
17 +== Proxy URL ==
18 +
19 +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.**
20 +
21 +
22 +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.
23 +
24 +* **HTTPS Proxy**
25 +{{code language="html"}}https://your-proxy.com:9000{{/code}}
26 +{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
27 +
28 +* **PAC Proxy**
29 +{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
30 +## ##
31 +
32 +----
33 +
34 +{{id name="desktop-previous"/}}
35 +
36 += Desktop 3.4.3 and previous versions =
37 +
38 +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"]].
39 +
40 +
4 4  {{id name="hostname"/}}
5 5  
6 -= Backend hostname =
43 +== Backend hostname ==
7 7  
8 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.
9 9  
... ... @@ -12,7 +12,7 @@
12 12  
13 13  {{id name="proxy"/}}
14 14  
15 -= Proxy server =
52 +== Proxy server ==
16 16  
17 17  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,7 +19,7 @@
19 19  
20 20  {{id name="proxyurl"/}}
21 21  
22 -== Apply proxy URL ==
59 +=== Apply proxy URL ===
23 23  
24 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.
25 25  
... ... @@ -40,7 +40,7 @@
40 40  
41 41  {{id name="systemproxy"/}}
42 42  
43 -== Use system proxy ==
80 +=== Use system proxy ===
44 44  
45 45  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.
46 46  
... ... @@ -47,7 +47,7 @@
47 47  
48 48  {{id name="certificate"/}}
49 49  
50 -= Server certificate =
87 +== Server certificate ==
51 51  
52 52  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.
53 53  
... ... @@ -54,7 +54,7 @@
54 54  
55 55  {{id name="customcertificatefile"/}}
56 56  
57 -== Choose custom certificate file ==
94 +=== Choose custom certificate file ===
58 58  
59 59  Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
60 60  
... ... @@ -68,7 +68,7 @@
68 68  
69 69  {{id name="systemcertificatechain"/}}
70 70  
71 -== Use system certificate chain (Windows) ==
108 +=== Use system certificate chain (Windows) ===
72 72  
73 73  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.
74 74