Toolpack:Tsbc TLS Profiles - Revision history

Allyntree at 16:40, 22 June 2024

2024-06-22T16:40:33Z

← Older revision		Revision as of 12:40, 22 June 2024
Line 8:		Line 8:
	\|-		\|-
	\|SBC		\|SBC
	\|3.1		\|3.1, 3.3
	\|}		\|}

Luc Morissette: /* List of Parameters */

2022-05-03T14:47:46Z

List of Parameters

← Older revision		Revision as of 10:47, 3 May 2022
Line 42:		Line 42:
	*[[Parameter: Require client authentication\|Require client authentication]]		*[[Parameter: Require client authentication\|Require client authentication]]
	*[[Parameter: Local certificate\|Local certificate]]		*[[Parameter: Local certificate\|Local certificate]]

			== References ==
			*[[TLS\|Information on TLS]]

Allyntree at 14:02, 15 December 2020

2020-12-15T14:02:14Z

← Older revision		Revision as of 10:02, 15 December 2020
Line 1:		Line 1:
			{{DISPLAYTITLE:Configuring TLS Profiles}}

	=== '''''~~Applies to version(s): v3.1~~''''' ~~===~~		{\| class="wikitable"
	~~{{DISPLAYTITLE:Configuring TLS Profiles}~~}		\|-
			\|rowspan="2"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|SBC
			\|3.1
			\|}

	Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], athough one TLS profile is generally enough.		Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], athough one TLS profile is generally enough.

Cbilodeau: re-arrange page

2019-09-05T20:47:20Z

re-arrange page

← Older revision		Revision as of 16:47, 5 September 2019
Line 18:		Line 18:

	* Provide a name that is meaningful to you.		* Provide a name that is meaningful to you.
	* ~~Decide~~ if client authentication is required. ~~This~~ means that incoming connections require the remote side to present a trusted certificate.		* Check if client authentication is required. Enabling this checkbox means that incoming connections require the remote side to present a or many trusted certificate(s) (later selected after creation).
	* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)		* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)
	* Click "Create"		* Click "Create"
	* Select one or multiple "trusted" certificates, which correspond to remote equipment's certificates (or root certificates from which remote certificates are signed)

	[[Image:ConfigureTlsProfile_2.png\|500px]]		[[Image:ConfigureTlsProfile_2.png\|500px]]

			* Select one or multiple "trusted" certificates, only necessary if "Require peer authentication" is checked.

	[[Image:ConfigureTlsProfile_3.png\|500px]]		[[Image:ConfigureTlsProfile_3.png\|500px]]

Cbilodeau: fix syntax

2019-03-22T15:38:00Z

fix syntax

← Older revision		Revision as of 11:38, 22 March 2019
Line 7:		Line 7:
	== Create TLS profile ==		== Create TLS profile ==

	1. Select '''TLS Profiles''' from the navigation panel ~~===~~		1. Select '''TLS Profiles''' from the navigation panel

	[[Image:ConfigureTlsProfile_0.png]]		[[Image:ConfigureTlsProfile_0.png]]

	2. Click ''' Create New TLS Profile''' ~~===~~		2. Click ''' Create New TLS Profile'''

	[[Image:ConfigureTlsProfile_1.png]]		[[Image:ConfigureTlsProfile_1.png]]

	3. Configure TLS Profile parameters ~~===~~		3. Configure TLS Profile parameters

	* Provide a name that is meaningful to you.		* Provide a name that is meaningful to you.
	* Decide if client authentication is required. This means that incoming connections require the remote side to present a trusted certificate.		* Decide if client authentication is required. This means that incoming connections require the remote side to present a trusted certificate.
	* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)/		* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)
	* Click "Create"		* Click "Create"
	* Select one or multiple "trusted" certificates, which correspond to remote equipment's certificates (or root certificates from which remote certificates are signed)		* Select one or multiple "trusted" certificates, which correspond to remote equipment's certificates (or root certificates from which remote certificates are signed)

Allyntree: /* Applies to version(s): v3.1 */

2019-03-15T16:58:35Z

Applies to version(s): v3.1

← Older revision		Revision as of 12:58, 15 March 2019
Line 3:		Line 3:
	{{DISPLAYTITLE:Configuring TLS Profiles}}		{{DISPLAYTITLE:Configuring TLS Profiles}}

	Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], ~~though~~ one TLS profile is generally enough.		Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], athough one TLS profile is generally enough.

	== Create TLS profile ==		== Create TLS profile ==

Allyntree: /* List of Parameters */

2019-03-15T15:19:40Z

List of Parameters

← Older revision		Revision as of 11:19, 15 March 2019
Line 31:		Line 31:

	*[[Parameter: Name\|Name]]		*[[Parameter: Name\|Name]]
			*[[Parameter: Require client authentication\|Require client authentication]]
			*[[Parameter: Local certificate\|Local certificate]]

Allyntree at 15:18, 15 March 2019

2019-03-15T15:18:41Z

← Older revision		Revision as of 11:18, 15 March 2019
Line 9:		Line 9:
	1. Select '''TLS Profiles''' from the navigation panel ===		1. Select '''TLS Profiles''' from the navigation panel ===

	[[Image:ConfigureTlsProfile_0.png~~\|150px~~]]		[[Image:ConfigureTlsProfile_0.png]]

	2. Click ''' Create New TLS Profile''' ===		2. Click ''' Create New TLS Profile''' ===

	[[Image:ConfigureTlsProfile_1.png~~\|300px~~]]		[[Image:ConfigureTlsProfile_1.png]]

	3. Configure TLS Profile parameters ===		3. Configure TLS Profile parameters ===

Allyntree at 14:50, 14 March 2019

2019-03-14T14:50:58Z

← Older revision		Revision as of 10:50, 14 March 2019
Line 1:		Line 1:
	~~Certificates are used to provide secure connections, like HTTPs (secure connection to the web portal) or [[FreeSBC]] secure SIP calls (SIP over TLS).~~

	~~This pages describes how to import certificates and group them into TLS profiles, which is the first step to configure secure SIP on [[FreeSBC]].~~		=== '''''Applies to version(s): v3.1''''' ===
			{{DISPLAYTITLE:Configuring TLS Profiles}}
	~~These TLS profiles can later be used to create SIP Transport servers using TLS.~~

	=~~= Configuring Certificates and TLS Profiles~~ ==
	~~{{DISPLAYTITLE:Configuring Certificates and TLS Profiles}}~~

	'''''Applies to version(s): v3.1 ~~and above~~'''''

	Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], though one TLS profile is generally enough.		Multiple TLS profiles can be created in [[Toolpack]]. A TLS profile is a collection of certificates and other settings that define the behavior of TLS connections. Multiple TLS profiles can be used to expose different certificates and options to different TLS connections in [[Toolpack]], though one TLS profile is generally enough.

	~~== Upload trusted certificates ==~~

	~~=== Select '''Certificates''' from the navigation panel ===~~

	~~[[Image:ConfigureCertificates_0.png\|150px]]~~

	~~=== Click ''' Create New Certificate ''' ===~~

	~~[[Image:ConfigureCertificates_1.png\|250px]]~~

	~~=== Configure certificate parameters ===~~

	* Give a name that is meaningful to you
	* Select "Trusted" certificate to import a remote party's certificate to trust
	* Drag-and-drop (or copy-paste) the certificate's text content into the appropriate text box
	* Click "Create"

	~~[[Image:ConfigureCertificates_2.png\|500px]]~~

	~~== Upload local certificates (optional) ==~~
	~~Toolpack already contains, by default, a unique self-signed certificate (unique per Toolpack system, shared for 1+1 hosts). This certificate is used for HTTPs, and can also be used for TLS.~~

	~~In case you want to use a custom local certificate (like an officially signed certificate for your domain name), proceed as follows:~~
	* Repeat the same procedure as above (but using "Local" certificate type) to import the local certificate
	* Use ssh (command-line or using tool like Filezilla) to upload the private key to the unit to following path. Use the '''same file''' name as the local certificate name previously used to import in the web portal (except file extension):
	~~/lib/tb/toolpack/pkg/ssl_certificate/~~

	~~Example:~~

	~~[[Image:ConfigureCertificates_3.png\|500px]]~~

	~~Then:~~
	~~scp my_local_cert.key root@MyFreeSbcHostName:/lib/tb/toolpack/pkg/ssl_certificate/~~

	== Create TLS profile ==		== Create TLS profile ==

	~~===~~ Select '''TLS Profiles''' from the navigation panel ===		1. Select '''TLS Profiles''' from the navigation panel ===

	[[Image:ConfigureTlsProfile_0.png\|150px]]		[[Image:ConfigureTlsProfile_0.png\|150px]]

	~~===~~ Click ''' Create New TLS Profile''' ===		2. Click ''' Create New TLS Profile''' ===

	[[Image:ConfigureTlsProfile_1.png\|300px]]		[[Image:ConfigureTlsProfile_1.png\|300px]]

	~~===~~ Configure TLS Profile parameters ===		3. Configure TLS Profile parameters ===

	* ~~Give~~ a name that is meaningful to you		* Provide a name that is meaningful to you.
	* Decide if client authentication is required ~~(meaning~~ that incoming connections require remote side to present a trusted certificate)		* Decide if client authentication is required. This means that incoming connections require the remote side to present a trusted certificate.
	* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)		* Select a local certificate (either one imported earlier, or the "Default" certificate which is automatically generated by Toolpack and is also used for HTTPS)/
	* Click "Create"		* Click "Create"
	* Select one or multiple "trusted" certificates, which correspond to remote equipment's certificates (or root certificates from which remote certificates are signed)		* Select one or multiple "trusted" certificates, which correspond to remote equipment's certificates (or root certificates from which remote certificates are signed)
Line 67:		Line 26:

	[[Image:ConfigureTlsProfile_3.png\|500px]]		[[Image:ConfigureTlsProfile_3.png\|500px]]


			== List of Parameters ==

			*[[Parameter: Name\|Name]]

Allyntree: /* Select Certificates from the navigation panel */

2019-03-12T14:51:40Z

Select Certificates from the navigation panel

← Older revision		Revision as of 10:51, 12 March 2019
Line 48:		Line 48:
	== Create TLS profile ==		== Create TLS profile ==

	=== Select '''~~Certificates~~''' from the navigation panel ===		=== Select '''TLS Profiles''' from the navigation panel ===

	[[Image:ConfigureTlsProfile_0.png\|150px]]		[[Image:ConfigureTlsProfile_0.png\|150px]]