Appboard/2.5/admin/ssl configuration - Revision history

imported>Dxturner: /* Existing Keys & Certificates */

2015-07-14T20:59:33Z

Existing Keys & Certificates

← Older revision		Revision as of 20:59, 14 July 2015
Line 42:		Line 42:
	#: You will be prompted to set a password, this '''must''' be set - do not leave blank. If you do not have any intermediate certificates then leave out the <tt>-CAfile</tt>, <tt>-caname</tt>, and <tt>-chain</tt> options.		#: You will be prompted to set a password, this '''must''' be set - do not leave blank. If you do not have any intermediate certificates then leave out the <tt>-CAfile</tt>, <tt>-caname</tt>, and <tt>-chain</tt> options.
	# Create a JKS from the <tt>combined.p12</tt> file generated above:		# Create a JKS from the <tt>combined.p12</tt> file generated above:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype ~~PCKS12~~ -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PKCS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).		#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below to ''Enable SSL & Installing the Keystore''.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below to ''Enable SSL & Installing the Keystore''.

imported>Jason.nicholls: /* Existing Keys & Certificates */

2015-03-20T09:08:38Z

Existing Keys & Certificates

← Older revision		Revision as of 09:08, 20 March 2015
Line 44:		Line 44:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).		#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on ''Enable SSL & Installing the Keystore''.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below to ''Enable SSL & Installing the Keystore''.

	For existing private key with signed certificate and intermediate certificates in PKCS#7 (.p7b) format follow these steps:		For existing private key with signed certificate and intermediate certificates in PKCS#7 (.p7b) format follow these steps:
Line 55:		Line 55:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).		#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on ''Enable SSL & Installing the Keystore''.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below to ''Enable SSL & Installing the Keystore''.

	=== Enable SSL & Install the Keystore ===		=== Enable SSL & Install the Keystore ===

imported>Jason.nicholls: /* Certificate & Keystore */

2015-03-20T09:07:45Z

Certificate & Keystore

← Older revision		Revision as of 09:07, 20 March 2015
Line 25:		Line 25:

	For SSL Tomcat requires a Java keystore containing the private key, signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.		For SSL Tomcat requires a Java keystore containing the private key, signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.


	==== New Certificates ====		==== New Certificates ====

	The recommended approach is to use <tt>keytool</tt> to create the private key, CSR, and keystore. The CA with then sign and provide a signed certificate along with their own certificate chain which can be imported into the keystore. Most CAs have this process well documented for popular web server platforms. Just follow the instructions for Tomcat such as these from VeriSign - and remember to refer back to this documentation on installing the keystore:		The recommended approach is to use <tt>keytool</tt> to create the private key, CSR, and keystore. The CA with then sign and provide a signed certificate along with their own certificate chain which can be imported into the keystore. Most CAs have this process well documented for popular web server platforms. Just follow the instructions for Tomcat such as these from VeriSign - and remember to refer back to this documentation on installing the keystore:

Line 34:		Line 32:
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)
	# Then follow the instructions below on ''Enable SSL & Installing the Keystore''		# Then follow the instructions below on ''Enable SSL & Installing the Keystore''


	==== Existing Keys & Certificates ====		==== Existing Keys & Certificates ====

	A limitation of keytool is that existing private keys cannot be imported. So for situations with an '''existing private key''', and regardless of the certificate format then it will be necessary to use <tt>openssl</tt> to do conversion.		A limitation of keytool is that existing private keys cannot be imported. So for situations with an '''existing private key''', and regardless of the certificate format then it will be necessary to use <tt>openssl</tt> to do conversion.

imported>Jason.nicholls: /* Certificate & Keystore */

2015-03-20T09:07:03Z

Certificate & Keystore

← Older revision		Revision as of 09:07, 20 March 2015
Line 24:		Line 24:
	=== Certificate & Keystore ===		=== Certificate & Keystore ===

	For SSL Tomcat requires a Java ~~KeyStore (JKS). The~~ keystore ~~needs to contain~~ the private key, ~~the~~ signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.		For SSL Tomcat requires a Java keystore containing the private key, signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.

	The recommended approach is to use <tt>keytool</tt> to create the private key ~~and~~ CSR and keystore ~~all in one go,~~ then ~~have the CA~~ sign, and ~~then import the~~ signed certificate ~~using PKCS#7 format directly~~ into the keystore. ~~This~~ process is well ~~outlined in~~ the VeriSign documentation ~~below~~:
			==== New Certificates ====

			The recommended approach is to use <tt>keytool</tt> to create the private key, CSR, and keystore. The CA with then sign and provide a signed certificate along with their own certificate chain which can be imported into the keystore. Most CAs have this process well documented for popular web server platforms. Just follow the instructions for Tomcat such as these from VeriSign - and remember to refer back to this documentation on installing the keystore:

	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing] (using keytool and creating a keystore in the process).		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing] (using keytool and creating a keystore in the process).
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)
	# Then follow the instructions below on ''Enable SSL & Installing the Keystore''.		# Then follow the instructions below on ''Enable SSL & Installing the Keystore''


			==== Existing Keys & Certificates ====

	~~However, if using~~ an existing private key, ~~signed~~ certificate~~, and intermediate certificates in X.509~~ format then ~~some conversion is required before importing into a JKS. This process~~ will ~~require~~ <tt>openssl</tt>.		A limitation of keytool is that existing private keys cannot be imported. So for situations with an '''existing private key''', and regardless of the certificate format then it will be necessary to use <tt>openssl</tt> to do conversion.

			For existing private key with signed certificate and intermediate certificates in X.509 format follow these steps:

	# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:		# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:
	#: <tt>openssl pkcs12 -export -in ''server_signed.crt'' -inkey ''private.key'' -CAfile ''ca.crt'' -caname root -chain -out combined.p12 -name ''your-alias''</tt>		#: <tt>openssl pkcs12 -export -in ''server_signed.crt'' -inkey ''private.key'' -CAfile ''ca.crt'' -caname root -chain -out combined.p12 -name ''your-alias''</tt>
	#: You will be prompted to ~~enter~~ a password, ~~make sure you~~ set ~~a password (~~do not leave blank). If you do not have any intermediate certificates then leave out the <tt>-CAfile</tt>, <tt>-caname</tt>, and <tt>-chain</tt> options.		#: You will be prompted to set a password, this '''must''' be set - do not leave blank. If you do not have any intermediate certificates then leave out the <tt>-CAfile</tt>, <tt>-caname</tt>, and <tt>-chain</tt> options.
			# Create a JKS from the <tt>combined.p12</tt> file generated above:
			#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
			#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
			# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on ''Enable SSL & Installing the Keystore''.

			For existing private key with signed certificate and intermediate certificates in PKCS#7 (.p7b) format follow these steps:
			# Convert the PKCS7 file (''certs.p7b'') to PEM encoded certificates:
			#: <tt>openssl pkcs7 -in ''certs.p7b'' -inform DER -print_certs -out ''certs.crt''</tt>
			# Convert the private key (''private.key'') and certificates (''certs.crt'' from above):
			#: <tt>openssl pkcs12 -export -in ''certs.crt'' -inkey ''private.key'' -out combined.p12 -name ''your-alias''</tt>
			#: You will be prompted to set a password, this '''must''' be set - do not leave blank.
	# Create a JKS from the <tt>combined.p12</tt> file generated above:		# Create a JKS from the <tt>combined.p12</tt> file generated above:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>

imported>Jason.nicholls: /* Certificate & Keystore */

2015-03-20T08:12:37Z

Certificate & Keystore

← Older revision		Revision as of 08:12, 20 March 2015
Line 32:		Line 32:
	# Then follow the instructions below on ''Enable SSL & Installing the Keystore''.		# Then follow the instructions below on ''Enable SSL & Installing the Keystore''.

	However, if ~~you already have~~ an existing private key, signed certificate, and intermediate certificates in X.509 format then some conversion is required before importing into a JKS. This process will require <tt>openssl</tt>.		However, if using an existing private key, signed certificate, and intermediate certificates in X.509 format then some conversion is required before importing into a JKS. This process will require <tt>openssl</tt>.

	# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:		# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:

imported>Jason.nicholls: /* Creating Certificate & Keystore */

2015-03-20T08:10:04Z

Creating Certificate & Keystore

← Older revision		Revision as of 08:10, 20 March 2015
Line 22:		Line 22:
	{{Note\|Due to the large variety of certificate authorities and key/certificate formats, this documentation does not cover all possibilities. If following instructions found elsewhere make sure to install the resulting keystore correctly for AppBoard (see the ''Enable SSL & Install the Keystore'' section).}}		{{Note\|Due to the large variety of certificate authorities and key/certificate formats, this documentation does not cover all possibilities. If following instructions found elsewhere make sure to install the resulting keystore correctly for AppBoard (see the ''Enable SSL & Install the Keystore'' section).}}

	=== ~~Creating~~ Certificate & Keystore ===		=== Certificate & Keystore ===

	For SSL Tomcat requires a Java KeyStore (JKS). The keystore needs to contain the private key, the signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.		For SSL Tomcat requires a Java KeyStore (JKS). The keystore needs to contain the private key, the signed certificate, and any intermediate certificates from the CA. To create and work with a keystore it is necessary to have Java installed and be able to run the <tt>keytool</tt> command.

imported>Jason.nicholls: /* Configuring AppBoard for SSL */

2015-03-20T08:09:25Z

Configuring AppBoard for SSL

imported>Jason.nicholls at 08:05, 20 March 2015

2015-03-20T08:05:26Z

← Older revision		Revision as of 08:05, 20 March 2015
Line 9:		Line 9:
	== Configuring AppBoard for SSL ==		== Configuring AppBoard for SSL ==

	~~To enable HTTPS (HTTP over SSL) mode use the <tt>HTTP_SSL</tt> runtime option and set it to <tt>true</tt>. In addition you may want to also change~~:		The overall process involves:

	* <tt>HTTP_PORT</tt>: ~~HTTPS is typically served on port 443~~		# Obtaining a signed certificate:
	* <tt>KEYSTORE_FILE</tt>: if ~~using your~~ own certificate		## Pick a Certificate Authority, this may be in-house if the organization has a Standard Operating Environment with their own root certificate installed on all systems. Otherwise this would be a commercial CA such as VeriSign, Thawte, or Go Daddy.
	* <tt>KEYSTORE_PASS</tt>: if using your own certificate		## Create a private key and Certificate Signing Request (CSR)
	* <tt>KEYSTORE_TYPE</tt>: if using your own certificate		## Have the CA sign the request
			## Download the signed certificate from the CA. Depending on the CA a variety of formats may be on offer. Choose an appropriate format for Tomcat - which the CA may explicitly list as an option, otherwise choose PKCS#7 format. Other formats may require additional conversion steps before Tomcat can make use of it.
			# Alternatively create a self-signed certificate. However, end-users will be presented with certificate errors and warnings as the certificate is not signed by a trusted authority.
			# Create a Java KeyStore (JKS) from the private key, signed certificate, and any intermediate certificates from the CA.
			# Install they keystore file on the AppBoard server.

	~~See the [[appboard/2.5/admin/runtime_options\|Runtime Options]] page for more information on these settings and how to configure them. After making any changes then restart the AppBoard service.~~		{{Note\|Due to the large variety of certificate authorities and key/certificate formats, this documentation cannot cover all options. If following instructions found elsewhere make sure to install the resulting keystore correctly for AppBoard (see the ''Install the Keystore'' section).}}

	{{~~Warning~~\|~~Do not configure SSL by editing the AppBoard server.xml file as this is a system file and replaced on upgrade. The correct way is~~ to ~~edit~~ the ~~runtime options.}}~~

	~~=== Process Overview ===~~

	~~The basic process is:~~

	~~# pick a Certificate Authority, this may be in-house if the organization has a Standard Operating Environment with their own root~~ certificate ~~installed on all systems. Otherwise this would be a commercial CA such as VeriSign, Thawte, or Go Daddy.~~
	~~# create a Certificate Signing Request (CSR)~~
	~~# have the CA sign the request~~
	~~# download the signed~~ certificate ~~from the CA. Depending on the CA a variety of~~ formats ~~may be on offer. Choose an appropriate format for Tomcat - which the CA may explicitly list as an option~~, ~~otherwise choose PKCS#7 format~~. ~~Other formats may require additional conversion steps before Tomcat can~~ make ~~use of it.~~
	~~# create a Java KeyStore (JKS) file for Tomcat and~~ install on the AppBoard ~~server.~~

	~~Another option is to generate a self-signed certificate to replace~~ the ~~self-signed certificate Edge ships with AppBoard. However, end-users will still be presented with certificate errors and warnings~~.

	=== Creating Certificate & Keystore ===		=== Creating Certificate & Keystore ===
Line 52:		Line 42:
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.

	=== ~~Installing~~ the Keystore ===		=== Enable SSL & Install the Keystore ===

	Once a valid keystore has been created it can be installed on the AppBoard server:		Once a valid keystore has been created it can be installed on the AppBoard server:

	# copy to the <tt>[INSTALL_HOME]/server/conf/ssl.crt/</tt> directory. By default files in this directory are automatically included in full archives.		# copy to the <tt>[INSTALL_HOME]/server/conf/ssl.crt/</tt> directory. By default files in this directory are automatically included in full archives.
	# Edit <tt>setenv-custom.sh\|.bat</tt> and update the <tt>KEYSTORE_FILE</tt>, <tt>KEYSTORE_PASS~~</tt>, and <tt>KEYSTORE_TYPE~~</tt> as required~~. If using the instructions above then the type should not need to be changed~~. Please note the keystore file path is relative to <tt>[INSTALL_HOME]/server/</tt>		# Edit <tt>setenv-custom.sh\|.bat</tt> and:
	# ~~As noted previously also make sure~~ the <tt>HTTP_SSL</tt> option ~~is set~~ to <tt>true</tt>.		## update the <tt>KEYSTORE_FILE</tt> and <tt>KEYSTORE_PASS</tt> as required. Please note the keystore file path is relative to <tt>[INSTALL_HOME]/server/</tt>
			## update the <tt>KEYSTORE_TYPE</tt> if using something other than Java KeyStore (JKS) format.
			## set the <tt>HTTP_SSL</tt> option to <tt>true</tt>.
			## (optionally) set the <tt>HTTP_PORT</tt> to the desired port.
	# Restart the AppBoard server.		# Restart the AppBoard server.

			See the [[appboard/2.5/admin/runtime_options\|Runtime Options]] page for complete information on all runtime options.

imported>Jason.nicholls: /* Creating Certificate & Keystore */

2015-03-20T07:33:22Z

Creating Certificate & Keystore

← Older revision		Revision as of 07:33, 20 March 2015
Line 46:		Line 46:
	# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:		# Convert the private key (''private.key''), signed certificate (''server_signed.crt''), and intermediate certificates (''ca.crt'') into PKCS#12 format:
	#: <tt>openssl pkcs12 -export -in ''server_signed.crt'' -inkey ''private.key'' -CAfile ''ca.crt'' -caname root -chain -out combined.p12 -name ''your-alias''</tt>		#: <tt>openssl pkcs12 -export -in ''server_signed.crt'' -inkey ''private.key'' -CAfile ''ca.crt'' -caname root -chain -out combined.p12 -name ''your-alias''</tt>
	#: You will be prompted to enter a password, make sure you set a password (do not leave blank).		#: You will be prompted to enter a password, make sure you set a password (do not leave blank). If you do not have any intermediate certificates then leave out the <tt>-CAfile</tt>, <tt>-caname</tt>, and <tt>-chain</tt> options.
	# Create a JKS from the <tt>combined.p12</tt> file generated above:		# Create a JKS from the <tt>combined.p12</tt> file generated above:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted to set a new password ~~and for the password from step (1)~~, ~~make sure to~~ use the same password ~~for both~~. ''your-alias'' must match the alias set in step (1).		#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.

imported>Jason.nicholls: /* Creating Certificate & Keystore */

2015-03-20T07:22:26Z

Creating Certificate & Keystore

← Older revision		Revision as of 07:22, 20 March 2015
Line 49:		Line 49:
	# Create a JKS from the <tt>combined.p12</tt> file generated above:		# Create a JKS from the <tt>combined.p12</tt> file generated above:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted to set a new password ~~for the JKS file,~~ and ~~prompted~~ for the password ~~set~~ from step (1) ~~- these must be~~ the same. ''your-alias'' must match the alias set in step (1).		#: You will be prompted to set a new password and for the password from step (1), make sure to use the same password for both. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.

← Older revision		Revision as of 08:09, 20 March 2015
Line 20:		Line 20:
	# Install they keystore file on the AppBoard server.		# Install they keystore file on the AppBoard server.

	{{Note\|Due to the large variety of certificate authorities and key/certificate formats, this documentation ~~cannot~~ cover all ~~options~~. If following instructions found elsewhere make sure to install the resulting keystore correctly for AppBoard (see the ''Install the Keystore'' section).}}		{{Note\|Due to the large variety of certificate authorities and key/certificate formats, this documentation does not cover all possibilities. If following instructions found elsewhere make sure to install the resulting keystore correctly for AppBoard (see the ''Enable SSL & Install the Keystore'' section).}}

	=== Creating Certificate & Keystore ===		=== Creating Certificate & Keystore ===
Line 30:		Line 30:
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing] (using keytool and creating a keystore in the process).		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing] (using keytool and creating a keystore in the process).
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore] (in PKCS#7 / .p7b format)
	# Then follow the instructions below on Installing the Keystore.		# Then follow the instructions below on ''Enable SSL & Installing the Keystore''.

	However, if you already have an existing private key, signed certificate, and intermediate certificates in X.509 format then some conversion is required before importing into a JKS. This process will require <tt>openssl</tt>.		However, if you already have an existing private key, signed certificate, and intermediate certificates in X.509 format then some conversion is required before importing into a JKS. This process will require <tt>openssl</tt>.
Line 40:		Line 40:
	#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>		#: <tt>keytool -importkeystore -srckeystore combined.p12 -srcstoretype PCKS12 -alias ''your-alias'' -destkeystore ''your-keystore.jks''</tt>
	#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).		#: You will be prompted for the password set above and a new password, you '''must''' use the same password. ''your-alias'' must match the alias set in step (1).
	# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on Installing the Keystore.		# Take the resulting JKS file (<tt>''your-keystore.jks''</tt>) and follow the instructions below on ''Enable SSL & Installing the Keystore''.

	=== Enable SSL & Install the Keystore ===		=== Enable SSL & Install the Keystore ===
Line 55:		Line 55:

	See the [[appboard/2.5/admin/runtime_options\|Runtime Options]] page for complete information on all runtime options.		See the [[appboard/2.5/admin/runtime_options\|Runtime Options]] page for complete information on all runtime options.


	== Redirecting HTTP traffic ==		== Redirecting HTTP traffic ==