Changes for page 3. Advanced Configurations

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-h. 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,21 +1,55 @@
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		-)))
	1	+= Desktop 4.0.0 or newer =
5	5
	3	+These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
6	6
	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	+
7	7	{{id name="hostname"/}}
8	8
9		-= Backend Hostname =
	43	+== Backend hostname ==
10	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.
	45	+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	12
13		-If your organisation is using the Teamwire Public Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
	47	+If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
14	14
15	15
16	16	{{id name="proxy"/}}
17	17
18		-= Proxy Server =
	52	+== Proxy server ==
19	19
20	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	21
...	...	@@ -22,7 +22,7 @@
22	22
23	23	{{id name="proxyurl"/}}
24	24
25		-== Apply Proxy URL ==
	59	+=== Apply proxy URL ===
26	26
27	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	28
...	...	@@ -39,19 +39,18 @@
39	39
40	40	* **PAC Proxy**
41	41	{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
42		-
43	43	## ##
44	44
45	45	{{id name="systemproxy"/}}
46	46
47		-== Use System Proxy ==
	80	+=== Use system proxy ===
48	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.
	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.
50	50
51	51
52	52	{{id name="certificate"/}}
53	53
54		-= Server Certificate =
	87	+== Server certificate ==
55	55
56	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	57
...	...	@@ -58,7 +58,7 @@
58	58
59	59	{{id name="customcertificatefile"/}}
60	60
61		-== Choose Custom Certificate File ==
	94	+=== Choose custom certificate file ===
62	62
63	63	Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
64	64
...	...	@@ -72,7 +72,7 @@
72	72
73	73	{{id name="systemcertificatechain"/}}
74	74
75		-== Use System Certificate Chain (Windows) ==
	108	+=== Use system certificate chain (Windows) ===
76	76
77	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	78