Wiki source code of 3. Advanced Configurations

Last modified by teamwire001 on 2024/12/12 14:41

version	line-number	content
2.1	1	= Desktop 4.0.0 or newer =
1.1	2
2.1	3	These settings are accessible during the [[Login and Registration process>>doc:Public.Applications.Desktop.User-Manual.Login-and-Registration.WebHome]].
1.1	4
2.1	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
3.1	36	= Desktop 3.4.3 and previous versions =
2.1	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
1.1	41	{{id name="hostname"/}}
	42
2.1	43	== Backend hostname ==
1.1	44
1.2	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.
1.1	46
1.2	47	If your organisation is using the Teamwire Cloud Backend, please enter {{code}}backend.teamwire.eu{{/code}}.
1.1	48
	49
	50	{{id name="proxy"/}}
	51
2.1	52	== Proxy server ==
1.1	53
	54	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.**
	55
	56
	57	{{id name="proxyurl"/}}
	58
2.1	59	=== Apply proxy URL ===
1.1	60
	61	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.
	62
	63	* HTTPS Proxy
	64	{{code language="html"}}https://your-proxy.com:9000{{/code}}
	65	{{code language="html"}}https://username:password@your-proxy.com:9000{{/code}}
	66
	67	* SOCKS-5 Proxy
	68	{{code language="html"}}socks5://your-proxy.com:9000{{/code}}
	69	{{code language="html"}}socks5://username:password@your-proxy.com:9000{{/code}}
	70
	71	* SOCKS-4 Proxy
	72	{{code language="html"}}socks4://your-proxy.com:9000{{/code}}
	73
	74	* PAC Proxy
	75	{{code language="html"}}pac+http://file-provider.com/proxy.pac{{/code}}
	76	## ##
	77
	78	{{id name="systemproxy"/}}
	79
2.1	80	=== Use system proxy ===
1.1	81
1.2	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.
1.1	83
	84
	85	{{id name="certificate"/}}
	86
2.1	87	== Server certificate ==
1.1	88
	89	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.
	90
	91
	92	{{id name="customcertificatefile"/}}
	93
2.1	94	=== Choose custom certificate file ===
1.1	95
	96	Click the button and select the file containing the server's certificate chain (format: ##PEM##) via the file explorer.
	97
	98	(% class="box infomessage" %)
	99	(((
	100	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.
	101
	102	Also note, that the path used to refer to your certificate must not contain any spaces.
	103	)))
	104
	105
	106	{{id name="systemcertificatechain"/}}
	107
3.1	108	=== Use system certificate chain (Windows) ===
1.1	109
	110	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.
	111
	112	## ##

Wiki source code of 3. Advanced Configurations

Last edited

Content