Appboard/2.4/admin/ssl configuration - Revision history

imported>Jason.nicholls: /* Additional Topics */

2014-09-05T13:02:30Z

Additional Topics

← Older revision		Revision as of 13:02, 5 September 2014
Line 45:		Line 45:

	* [[appboard/2.4/admin/untrusted_ssl_ios\|Untrusted Certificates on iOS mobile devices]]		* [[appboard/2.4/admin/untrusted_ssl_ios\|Untrusted Certificates on iOS mobile devices]]
	~~<!--~~* [[appboard/2.4/admin/client_certificates\|Client Certificates / Client Authentication]]~~-->~~		* [[appboard/2.4/admin/client_certificates\|Client Certificates / Client Authentication]]

imported>Jason.nicholls: /* Additional Topics */

2014-07-24T06:43:13Z

Additional Topics

← Older revision		Revision as of 06:43, 24 July 2014
Line 45:		Line 45:

	* [[appboard/2.4/admin/untrusted_ssl_ios\|Untrusted Certificates on iOS mobile devices]]		* [[appboard/2.4/admin/untrusted_ssl_ios\|Untrusted Certificates on iOS mobile devices]]
	* [[appboard/2.4/admin/client_certificates\|Client Certificates / Client Authentication]]		<!--* [[appboard/2.4/admin/client_certificates\|Client Certificates / Client Authentication]]-->

imported>Andy.hopper: /* Redirecting HTTP traffic */

2014-04-08T15:46:34Z

Redirecting HTTP traffic

← Older revision		Revision as of 15:46, 8 April 2014
Line 38:		Line 38:
	There are two recommended approaches for redirecting standard HTTP traffic to HTTPS:		There are two recommended approaches for redirecting standard HTTP traffic to HTTPS:

	# Use external tool to redirect the traffic such as a load balancer or a full featured HTTP server like ~~Apachet~~. For many this will be the preferred option as since no configuration changes to enPortal/AppBoard are necessary.		# Use an external tool to redirect the traffic such as a load balancer or a full featured HTTP server like [http://httpd.apache.org/ Apache]. For many this will be the preferred option as since no configuration changes to enPortal/AppBoard are necessary.

	# Modify <tt>server/conf/server.xml</tt> and <tt>server/webapps/enportal/WEB-INF/web.xml</tt> to define an extra non-SSL connector that will redirect to the HTTPS port. This approach is [https://www.google.com/search?q=tomcat+web.xml+http+connector+forward+https&oq=tomcat+web.xml+http+connector+forward+https&aqs=chrome..69i57.12323j0j7&sourceid=chrome&es_sm=91&ie=UTF-8#q=tomcat+redirect+http+to+https&safe=active well documented by the Tomcat user community].		# Modify <tt>server/conf/server.xml</tt> and <tt>server/webapps/enportal/WEB-INF/web.xml</tt> to define an extra non-SSL connector that will redirect to the HTTPS port. This approach is [https://www.google.com/search?q=tomcat+web.xml+http+connector+forward+https&oq=tomcat+web.xml+http+connector+forward+https&aqs=chrome..69i57.12323j0j7&sourceid=chrome&es_sm=91&ie=UTF-8#q=tomcat+redirect+http+to+https&safe=active well documented by the Tomcat user community].

imported>Andy.hopper at 15:45, 8 April 2014

2014-04-08T15:45:07Z

← Older revision		Revision as of 15:45, 8 April 2014
Line 34:		Line 34:
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore]. NOTE: as mentioned previously do not edit server.xml directly, use the runtime options as documented above.		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore]. NOTE: as mentioned previously do not edit server.xml directly, use the runtime options as documented above.

			== Redirecting HTTP traffic ==

			There are two recommended approaches for redirecting standard HTTP traffic to HTTPS:

			# Use external tool to redirect the traffic such as a load balancer or a full featured HTTP server like Apachet. For many this will be the preferred option as since no configuration changes to enPortal/AppBoard are necessary.

			# Modify <tt>server/conf/server.xml</tt> and <tt>server/webapps/enportal/WEB-INF/web.xml</tt> to define an extra non-SSL connector that will redirect to the HTTPS port. This approach is [https://www.google.com/search?q=tomcat+web.xml+http+connector+forward+https&oq=tomcat+web.xml+http+connector+forward+https&aqs=chrome..69i57.12323j0j7&sourceid=chrome&es_sm=91&ie=UTF-8#q=tomcat+redirect+http+to+https&safe=active well documented by the Tomcat user community].

	== Additional Topics ==		== Additional Topics ==

imported>Jason.nicholls at 06:53, 1 April 2014

2014-04-01T06:53:02Z

← Older revision		Revision as of 06:53, 1 April 2014
Line 14:		Line 14:
	* <tt>KEYSTORE_TYPE</tt>: if using your own certificate		* <tt>KEYSTORE_TYPE</tt>: if using your own certificate

	See the [[~~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.		See the [[appboard/2.4/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.

	{{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.}}		{{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.}}

imported>Jason.nicholls at 06:42, 14 December 2013

2013-12-14T06:42:20Z

← Older revision		Revision as of 06:42, 14 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:SSL Configuration}}		{{DISPLAYTITLE:SSL Configuration}}
			[[Category:AppBoard 2.4]]
	For security reasons it's recommended to run AppBoard over SSL (Secure Socket Layer). This will ensure all communications between clients (browsers) and the AppBoard server are encrypted.		For security reasons it's recommended to run AppBoard over SSL (Secure Socket Layer). This will ensure all communications between clients (browsers) and the AppBoard server are encrypted.

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

2013-10-01T04:37:05Z

Configuring AppBoard for SSL

← Older revision		Revision as of 04:37, 1 October 2013
Line 13:		Line 13:
	* <tt>KEYSTORE_TYPE</tt>: if using your own certificate		* <tt>KEYSTORE_TYPE</tt>: if using your own certificate

	See the [[Runtime_Options\|Runtime Options]] page for more information on these settings and how to configure them.		See the [[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.

	{{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.}}		{{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.}}

imported>Jason.nicholls: /* Additional Topics */

2013-10-01T04:28:42Z

Additional Topics

← Older revision		Revision as of 04:28, 1 October 2013
Line 36:		Line 36:
	== Additional Topics ==		== Additional Topics ==

	* Untrusted Certificates on iOS mobile devices		* [[appboard/2.4/admin/untrusted_ssl_ios\|Untrusted Certificates on iOS mobile devices]]
	* Client Certificates / Client Authentication		* [[appboard/2.4/admin/client_certificates\|Client Certificates / Client Authentication]]

imported>Jason.nicholls at 04:27, 1 October 2013

2013-10-01T04:27:02Z

← Older revision		Revision as of 04:27, 1 October 2013
Line 32:		Line 32:
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing].		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR227 creating a CSR and submitting for signing].
	# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore]. NOTE: as mentioned previously do not edit server.xml directly, use the runtime options as documented above.		# [https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR153 importing the signed certificate into a JKS keystore]. NOTE: as mentioned previously do not edit server.xml directly, use the runtime options as documented above.


			== Additional Topics ==

			* Untrusted Certificates on iOS mobile devices
			* Client Certificates / Client Authentication

imported>Jason.nicholls: /* Creating A Certificate */

2013-10-01T04:21:29Z

Creating A Certificate

← Older revision		Revision as of 04:21, 1 October 2013
Line 17:		Line 17:
	{{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.}}		{{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.}}

	== Creating A Certificate ==		== Creating a Certificate ==

	The basic process is:		The basic process is: