Skip to Content

Wiki source code of 3. Advanced Configurations

Version 1.4 by teamwire001 on 2023/02/10 13:49
Show last authors
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
3
4 {{id name="hostname"/}}
5
6 = Backend hostname =
7
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
10 If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
11
12
13 {{id name="proxy"/}}
14
15 = Proxy server =
16
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
19
20 {{id name="proxyurl"/}}
21
22 == Apply proxy URL ==
23
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
26 * **HTTPS Proxy**
27 {{code language="html"}}https://your-proxy.com:9000{{/code}}
28 {{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
29
30 * **SOCKS-5 Proxy**
31 {{code language="html"}}socks5://your-proxy.com:9000{{/code}}
32 {{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}}
33
34 * **SOCKS-4 Proxy**
35 {{code language="html"}}socks4://your-proxy.com:9000{{/code}}
36
37 * **PAC Proxy**
38 {{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
39 ## ##
40
41 {{id name="systemproxy"/}}
42
43 == Use system proxy ==
44
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
47
48 {{id name="certificate"/}}
49
50 = Server certificate =
51
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
54
55 {{id name="customcertificatefile"/}}
56
57 == Choose custom certificate file ==
58
59 Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
60
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.
64
65 Also note, that the path used to refer to your certificate must not contain any spaces.
66 )))
67
68
69 {{id name="systemcertificatechain"/}}
70
71 == Use system certificate chain (Windows) ==
72
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
75 ## ##