Wiki source code of h. Advanced Configurations
Version 1.1 by teamwire001 on 2021/06/10 09:56
Show last authors
author | version | line-number | content |
---|---|---|---|
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 | ))) | ||
5 | |||
6 | |||
7 | {{id name="hostname"/}} | ||
8 | |||
9 | = Backend Hostname = | ||
10 | |||
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. | ||
12 | |||
13 | If your organisation is using the Teamwire Public Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}. | ||
14 | |||
15 | |||
16 | {{id name="proxy"/}} | ||
17 | |||
18 | = Proxy Server = | ||
19 | |||
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.** | ||
21 | |||
22 | |||
23 | {{id name="proxyurl"/}} | ||
24 | |||
25 | == Apply Proxy URL == | ||
26 | |||
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. | ||
28 | |||
29 | * **HTTPS Proxy** | ||
30 | {{code language="html"}}https://your-proxy.com:9000{{/code}} | ||
31 | {{code language="html"}}https://username:password@your-proxy.com:9000{{/code}} | ||
32 | |||
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 | |||
40 | * **PAC Proxy** | ||
41 | {{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}} | ||
42 | |||
43 | ## ## | ||
44 | |||
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 | |||
52 | {{id name="certificate"/}} | ||
53 | |||
54 | = Server Certificate = | ||
55 | |||
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. | ||
57 | |||
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 | |||
79 | ## ## |