Appboard/2.5/admin/client certificates - Revision history

imported>Jason.nicholls: /* Configure AppBoard for Client Authentication */

2014-09-05T13:07:25Z

Configure AppBoard for Client Authentication

← Older revision		Revision as of 13:07, 5 September 2014
Line 10:		Line 10:
	# (optionally) AppBoard may be customized to use this information beyond Tomcat validating the SSL session.		# (optionally) AppBoard may be customized to use this information beyond Tomcat validating the SSL session.

	== ~~Configure AppBoard for~~ Client Authentication ==		== Enabling Client Authentication ==

	To enable HTTPS Client Authentication the first step is to enable HTTPS and have that working correctly. With that enabled the following runtime options also need to be set:		To enable HTTPS Client Authentication the first step is to enable HTTPS and have that working correctly. With that enabled the following runtime options also need to be set:

imported>Jason.nicholls: /* Tomcat Configuration */

2014-09-05T13:07:07Z

Tomcat Configuration

← Older revision		Revision as of 13:07, 5 September 2014
Line 10:		Line 10:
	# (optionally) AppBoard may be customized to use this information beyond Tomcat validating the SSL session.		# (optionally) AppBoard may be customized to use this information beyond Tomcat validating the SSL session.

	== ~~Tomcat Configuration~~ ==		== Configure AppBoard for Client Authentication ==

	~~# Enable client authentication by editing <tt>[INSTALL_HOME]/server/conf/server~~.~~xml</tt> and adding~~ the following ~~parameters~~ to ~~the eportal Connector~~:		To enable HTTPS Client Authentication the first step is to enable HTTPS and have that working correctly. With that enabled the following runtime options also need to be set:
	#: <tt>~~clientAuth="true"~~</tt>
	#: <tt>~~truststoreFile="''full_path_to_truststore_file''"~~</tt>		* <tt>CLIENTAUTH</tt>: set this to <tt>true</tt>
	#: <tt>~~truststorePass="''password_for_truststore_file''"~~</tt>		* <tt>TRUSTSTORE_FILE</tt>: required if client authentication is enabled.
	~~# Create a Java Truststore file in JKS format, alternatively PKCS11 and PKCS12 are supported by setting the~~ <tt>~~truststoreType~~</tt> ~~parameter~~. ~~By default the type used matches the~~ <tt>~~keystoreType~~</tt> ~~parameter~~.		* <tt>TRUSTSTORE_PASS</tt>: if the truststore is password protected.
			* <tt>TRUSTSTORE_TYPE</tt>: to identify the type of truststore file.

			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\|It is recommended to contact Support and engage the Edge Solutions team to help with the basic configuration and further customization that may be needed.}}		{{Note\|It is recommended to contact Support and engage the Edge Solutions team to help with the basic configuration and further customization that may be needed.}}

imported>Jason.nicholls: Created page with '{{DISPLAYTITLE:Client Certificates / Client Authentication}} Category:AppBoard 2.5 ==Overview== Most people are familiar with secure web sites, sites that begin with the addr…'

2014-07-24T07:39:04Z

Created page with '{{DISPLAYTITLE:Client Certificates / Client Authentication}} Category:AppBoard 2.5 ==Overview== Most people are familiar with secure web sites, sites that begin with the addr…'

New page

{{DISPLAYTITLE:Client Certificates / Client Authentication}}
[[Category:AppBoard 2.5]]
==Overview==
Most people are familiar with secure web sites, sites that begin with the address <tt>https</tt>, that use certificates signed by authorities trusted to ensure the site is who it says it is. Lesser known is the server can request the client return a certificate to authenticate the client - this is known as (SSL) ''Client Authentication''

AppBoard fully supports SSL Client Authentication and the main components to configure are:

# Update Tomcat to enable client authentication
# Create/Import Java Truststore used by the server to validate the client certificates.
# (optionally) AppBoard may be customized to use this information beyond Tomcat validating the SSL session.

== Tomcat Configuration ==

# Enable client authentication by editing <tt>[INSTALL_HOME]/server/conf/server.xml</tt> and adding the following parameters to the eportal Connector:
#: <tt>clientAuth="true"</tt>
#: <tt>truststoreFile="''full_path_to_truststore_file''"</tt>
#: <tt>truststorePass="''password_for_truststore_file''"</tt>
# Create a Java Truststore file in JKS format, alternatively PKCS11 and PKCS12 are supported by setting the <tt>truststoreType</tt> parameter. By default the type used matches the <tt>keystoreType</tt> parameter.

{{Note|It is recommended to contact Support and engage the Edge Solutions team to help with the basic configuration and further customization that may be needed.}}