Using SSL with Web Interface - Revision history

Dina: /* SSL Troubleshooting */

2020-07-09T06:29:00Z

SSL Troubleshooting

← Older revision		Revision as of 06:29, 9 July 2020
Line 112:		Line 112:

	*'''Splitting the .pem file'''		*'''Splitting the .pem file'''
	Now it is time to split the newly created .pem file into the different files required by ~~CRM~~ Web Interface.		Now it is time to split the newly created .pem file into the different files required by RangerMSP Web Interface.

	If you examine the new .pem file with Notepad, you will notice that it consists of two parts:		If you examine the new .pem file with Notepad, you will notice that it consists of two parts:

Dina at 13:53, 8 July 2020

2020-07-08T13:53:53Z

Dina at 10:52, 19 June 2020

2020-06-19T10:52:08Z

← Older revision		Revision as of 10:52, 19 June 2020
Line 101:		Line 101:

	*'''Convert the exported .pfx file to a .pem format'''		*'''Convert the exported .pfx file to a .pem format'''
	To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from CommitCRM's web site at the following URL:<br>http://{{SERVERNAME}}downloads/openssl.exe		To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from CommitCRM's web site at the following URL:<br>http://{{SERVERNAME}}/downloads/openssl.exe

	After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:		After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:

Dina at 10:27, 19 June 2020

2020-06-19T10:27:25Z

← Older revision		Revision as of 10:27, 19 June 2020
Line 101:		Line 101:

	*'''Convert the exported .pfx file to a .pem format'''		*'''Convert the exported .pfx file to a .pem format'''
	To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from CommitCRM's web site at the following URL:<br>http://~~www.CommitCRM.com/~~downloads/openssl.exe		To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from CommitCRM's web site at the following URL:<br>http://{{SERVERNAME}}downloads/openssl.exe

	After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:		After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:

Sheli at 10:36, 3 July 2015

2015-07-03T10:36:45Z

← Older revision		Revision as of 10:36, 3 July 2015
Line 1:		Line 1:
	{{usermanualswebinterface}}		{{usermanualswebinterface}}

	CommitCRM Web ~~Interface supports~~ the ~~ability to accept~~ SSL ~~connections (https rather than http)~~.		To configure CommitCRM with SSL you need to be using Microsoft IIS as the back end Web server for the Web interface.<br>
			Then - install and configure your SSL certificates in Microsoft IIS.

	~~Using SSL with~~ CommitCRM ~~Web Interface is OPTIONAL. You can~~ use CommitCRM Web ~~Interface without setting up SSL~~.		CommitCRM version 9, and above, are required in order to use Microsoft IIS with CommitCRM Web interface.

	~~The first step you should take if you want to use SSL with CommitCRM~~ Web Interface ~~is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.~~		>>> Continue here: '''[[Microsoft_IIS_as_the_Web_Server_for_the_Web_Interface\|Using Microsoft IIS as the Web Server for the Web Interface]]'''

	~~If you'd like to read a~~ SSL ~~Certificate creation tutorial~~, ~~[[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]]~~.		<br>
			<br>
			<br>
			<pre style="color: red">
			THE FOLLOWING ARE THE OLD INSTRUCTIONS ON HOW TO USE SSL WITH CommitCRM version 8 (or below).
			THIS OLD METHOD MIGHT BE EXPOSED TO VULNERABILITIES DISCOVERED IN THE SSL3 PROTOCOL AND SHOULD NOT BE USED ANYMORE.
			Instead - Use CommitCRM version 9, or above, together with Microsoft IIS as its back end Web server.
			</pre>

			CommitCRM Web Interface supports the ability to accept SSL connections (https rather than http).

	~~UPDATE: 01/2015 - The newest versions of Chrome and Firefox block connections to the~~ Web ~~interface over SSL. This~~ is ~~the result of a recently discovered vulnerability in the SSL (version 3) protocol~~. Everything works well when using Microsoft Internet Explorer (IE) as well as when not using the newest versions of Chrome and Firefox. At this time version 3 of SSL cannot be disabled. The next version of CommitCRM ~~will introduce an option to use Microsoft IIS as the backend~~ Web ~~server for the Web interface and as a result the latest Chrome and Firefox will also work~~.		Using SSL with CommitCRM Web Interface is OPTIONAL. You can use CommitCRM Web Interface without setting up SSL.

			The first step you should take if you want to use SSL with CommitCRM Web Interface is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.

	== Saving the Certificates Files ==		== Saving the Certificates Files ==
Line 27:		Line 37:
	Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.		Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.

			If you'd like to read a SSL Certificate creation tutorial, [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]].
	<br>		<br>

Sheli at 08:22, 28 January 2015

2015-01-28T08:22:09Z

← Older revision		Revision as of 08:22, 28 January 2015
Line 10:		Line 10:


	UPDATE: 01/2015 - The newest versions of Chrome and Firefox block connections to the Web interface over SSL. This is the result of of a recently discovered vulnerability in the SSL (version 3) protocol. Everything works well when using Microsoft Internet Explorer (IE) as well as when not using the newest versions of Chrome and Firefox. At this time version 3 of SSL cannot be disabled. The next version of CommitCRM will introduce an option to use Microsoft IIS as the backend Web server for the Web interface and as a result the latest Chrome and Firefox will also work.		UPDATE: 01/2015 - The newest versions of Chrome and Firefox block connections to the Web interface over SSL. This is the result of a recently discovered vulnerability in the SSL (version 3) protocol. Everything works well when using Microsoft Internet Explorer (IE) as well as when not using the newest versions of Chrome and Firefox. At this time version 3 of SSL cannot be disabled. The next version of CommitCRM will introduce an option to use Microsoft IIS as the backend Web server for the Web interface and as a result the latest Chrome and Firefox will also work.

Sheli at 08:18, 28 January 2015

2015-01-28T08:18:45Z

← Older revision		Revision as of 08:18, 28 January 2015
Line 8:		Line 8:

	If you'd like to read a SSL Certificate creation tutorial, [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]].		If you'd like to read a SSL Certificate creation tutorial, [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]].


			UPDATE: 01/2015 - The newest versions of Chrome and Firefox block connections to the Web interface over SSL. This is the result of of a recently discovered vulnerability in the SSL (version 3) protocol. Everything works well when using Microsoft Internet Explorer (IE) as well as when not using the newest versions of Chrome and Firefox. At this time version 3 of SSL cannot be disabled. The next version of CommitCRM will introduce an option to use Microsoft IIS as the backend Web server for the Web interface and as a result the latest Chrome and Firefox will also work.

Robert: /* Saving the Certificates Files */

2014-04-08T08:55:12Z

Saving the Certificates Files

← Older revision		Revision as of 08:55, 8 April 2014
Line 20:		Line 20:
	<Installation_DIR>\CommitCRM\WebInterface		<Installation_DIR>\CommitCRM\WebInterface

	If your certificates are in another file format, convert them to the .pem file format.		<br>
			'''If your certificates are in another file format, convert them to the .pem file format.'''
	Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.		Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.

			<br>

	== Activating SSL with CommitCRM ==		== Activating SSL with CommitCRM ==

Robert: /* See Also */

2013-09-23T07:05:56Z

Robert at 09:45, 29 August 2013

2013-08-29T09:45:55Z

← Older revision		Revision as of 07:05, 23 September 2013
Line 120:		Line 120:
	*[[Web Interface]]		*[[Web Interface]]
	*[[Troubleshooting]]		*[[Troubleshooting]]
			*[[Using StartSSL Certificates]]

	[[Category:Installation]]		[[Category:Installation]]
	[[Category:Web Interface]]		[[Category:Web Interface]]

← Older revision		Revision as of 13:53, 8 July 2020
Line 1:		Line 1:
	{{usermanualswebinterface}}		{{usermanualswebinterface}}

	To configure ~~CommitCRM~~ with SSL you need to be using Microsoft IIS as the back end Web server for the Web interface.<br>		To configure RangerMSP with SSL you need to be using Microsoft IIS as the back end Web server for the Web interface.<br>
	Then - install and configure your SSL certificates in Microsoft IIS.		Then - install and configure your SSL certificates in Microsoft IIS.

	~~CommitCRM~~ version 9, and above, are required in order to use Microsoft IIS with ~~CommitCRM~~ Web interface.		RangerMSP version 9, and above, are required in order to use Microsoft IIS with RangerMSP Web interface.

	>>> Continue here: '''[[Microsoft_IIS_as_the_Web_Server_for_the_Web_Interface\|Using Microsoft IIS as the Web Server for the Web Interface]]'''		>>> Continue here: '''[[Microsoft_IIS_as_the_Web_Server_for_the_Web_Interface\|Using Microsoft IIS as the Web Server for the Web Interface]]'''
Line 12:		Line 12:
	<br>		<br>
	<pre style="color: red">		<pre style="color: red">
	THE FOLLOWING ARE THE OLD INSTRUCTIONS ON HOW TO USE SSL WITH ~~CommitCRM~~ version 8 (or below).		THE FOLLOWING ARE THE OLD INSTRUCTIONS ON HOW TO USE SSL WITH RangerMSP version 8 (or below).
	THIS OLD METHOD MIGHT BE EXPOSED TO VULNERABILITIES DISCOVERED IN THE SSL3 PROTOCOL AND SHOULD NOT BE USED ANYMORE.		THIS OLD METHOD MIGHT BE EXPOSED TO VULNERABILITIES DISCOVERED IN THE SSL3 PROTOCOL AND SHOULD NOT BE USED ANYMORE.
	Instead - Use ~~CommitCRM~~ version 9, or above, together with Microsoft IIS as its back end Web server.		Instead - Use RangerMSP version 9, or above, together with Microsoft IIS as its back end Web server.
	</pre>		</pre>

	~~CommitCRM~~ Web Interface supports the ability to accept SSL connections (https rather than http).		RangerMSP Web Interface supports the ability to accept SSL connections (https rather than http).

	Using SSL with ~~CommitCRM~~ Web Interface is OPTIONAL. You can use ~~CommitCRM~~ Web Interface without setting up SSL.		Using SSL with RangerMSP Web Interface is OPTIONAL. You can use RangerMSP Web Interface without setting up SSL.

	The first step you should take if you want to use SSL with ~~CommitCRM~~ Web Interface is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.		The first step you should take if you want to use SSL with RangerMSP Web Interface is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.

	== Saving the Certificates Files ==		== Saving the Certificates Files ==
	~~CommitCRM~~ requires that your certificates files be in the .pem file format.		RangerMSP requires that your certificates files be in the .pem file format.
	You should have three certificates files with the following names:		You should have three certificates files with the following names:

Line 31:		Line 31:
	Place your certificates files in the following folder:		Place your certificates files in the following folder:

	<Installation_DIR>\~~CommitCRM~~\WebInterface		<Installation_DIR>\RangerMSP\WebInterface

	<br>		<br>
Line 40:		Line 40:
	<br>		<br>

	== Activating SSL with ~~CommitCRM~~ ==		== Activating SSL with RangerMSP ==
	You need to instruct ~~CommitCRM~~ Web Interface to use SSL. To do so, you must edit the following file:<br><Installation_DIR>\~~CommitCRM~~\WebInterface\~~CommitWebInterface~~.ini		You need to instruct RangerMSP Web Interface to use SSL. To do so, you must edit the following file:<br><Installation_DIR>\RangerMSP\WebInterface\CRMWebInterface.ini

	Change the token settings in the above file to Yes as follows:<br>UseSSLEncryption=Y		Change the token settings in the above file to Yes as follows:<br>UseSSLEncryption=Y

	== Setting the SSL Port ==		== Setting the SSL Port ==
	The SSL communication between users/browsers and ~~CommitCRM~~ Web Interface uses a dedicated port.		The SSL communication between users/browsers and RangerMSP Web Interface uses a dedicated port.

	Set a port number for ~~CommitCRM~~ Web Interface. This port should not be in use by any other application or service.		Set a port number for RangerMSP Web Interface. This port should not be in use by any other application or service.

	We recommend using the ~~CommitCRM~~ default port for SSL: 4962.		We recommend using the RangerMSP default port for SSL: 4962.

	If you decide to use another port, make sure that:		If you decide to use another port, make sure that:
Line 56:		Line 56:
	#You select a port value other than the standard SSL port (443) which is probably already in use on your server (by IIS for example).		#You select a port value other than the standard SSL port (443) which is probably already in use on your server (by IIS for example).

	To configure the SSL port, set the SSLPort token value in the following settings file:<br><Installation_DIR>\~~CommitCRM~~\WebInterface\~~CommitWebInterface~~.ini		To configure the SSL port, set the SSLPort token value in the following settings file:<br><Installation_DIR>\RangerMSP\WebInterface\CRMWebInterface.ini

	<u>Important Note:</u><br>If you use a firewall, proxy, etc., it is recommended that you open Port 4962 in order to allow a connection to be established with ~~CommitCRM~~ Web Interface.<br>If this port is blocked by a firewall, a connection cannot be established.		<u>Important Note:</u><br>If you use a firewall, proxy, etc., it is recommended that you open Port 4962 in order to allow a connection to be established with RangerMSP Web Interface.<br>If this port is blocked by a firewall, a connection cannot be established.

	== Setting SSL Certificate Password ==		== Setting SSL Certificate Password ==
	If you have a password for your SSL Certificate (SSL Certificate passwords are optional), enter the password for the SSlPassword token in:<br><Installation_DIR>\~~CommitCRM~~\WebInterface\~~CommitWebInterface~~.ini		If you have a password for your SSL Certificate (SSL Certificate passwords are optional), enter the password for the SSlPassword token in:<br><Installation_DIR>\RangerMSP\WebInterface\CRMWebInterface.ini

	== Modifying the Login Page to Use SSL ==		== Modifying the Login Page to Use SSL ==
Line 89:		Line 89:

	*'''General Information'''		*'''General Information'''
	This issue is relevant only when you configure ~~CommitCRM~~ Web Interface to use SSL. ~~CommitCRM~~ requires that your certificate files all have the .pem format.		This issue is relevant only when you configure RangerMSP Web Interface to use SSL. RangerMSP requires that your certificate files all have the .pem format.

	If your certificates are in another format, convert them to the .pem format by following these instructions:		If your certificates are in another format, convert them to the .pem format by following these instructions:
Line 101:		Line 101:

	*'''Convert the exported .pfx file to a .pem format'''		*'''Convert the exported .pfx file to a .pem format'''
	To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from ~~CommitCRM~~'s web site at the following URL:<br>http://{{SERVERNAME}}/downloads/openssl.exe		To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from RangerMSP's web site at the following URL:<br>http://{{SERVERNAME}}/downloads/openssl.exe

	After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:		After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:
Line 109:		Line 109:
	Where <your file> is the name of the file created during the export phase.		Where <your file> is the name of the file created during the export phase.

	Openssl.exe will prompt you for a password. Enter it if you used one during the export phase, or leave it blank if you did not specify one.<br>It will also prompt you for a new password for the .pem file. This is optional, but if you protect it with a password be sure to enter the SSLPassword token in the ~~CommitWebInterface~~.ini file as explained above.		Openssl.exe will prompt you for a password. Enter it if you used one during the export phase, or leave it blank if you did not specify one.<br>It will also prompt you for a new password for the .pem file. This is optional, but if you protect it with a password be sure to enter the SSLPassword token in the CRMWebInterface.ini file as explained above.

	*'''Splitting the .pem file'''		*'''Splitting the .pem file'''
	Now it is time to split the newly created .pem file into the different files required by ~~Commit~~ Web Interface.		Now it is time to split the newly created .pem file into the different files required by CRM Web Interface.

	If you examine the new .pem file with Notepad, you will notice that it consists of two parts:		If you examine the new .pem file with Notepad, you will notice that it consists of two parts:
Line 132:		Line 132:
	The final stage is to obtain the Root.pem file.<br>This is the Certificate Authority certificate file. You can obtain this from Internet Explorer > Tools > Internet Options.<br>Navigate to the Content tab and click on Certificates.<br>In Trusted Root Certificate Authority tab, select the Authority that issued your certificate and the Export it in Base64 (cer) format.		The final stage is to obtain the Root.pem file.<br>This is the Certificate Authority certificate file. You can obtain this from Internet Explorer > Tools > Internet Options.<br>Navigate to the Content tab and click on Certificates.<br>In Trusted Root Certificate Authority tab, select the Authority that issued your certificate and the Export it in Base64 (cer) format.

	The exported file format is the SAME as the .pem format, so after exporting it simply rename the file Root.pem and save it with the other certificate file in folder<br><Installation_DIR>\~~CommitCRM~~\WebInterface		The exported file format is the SAME as the .pem format, so after exporting it simply rename the file Root.pem and save it with the other certificate file in folder<br><Installation_DIR>\RangerMSP\WebInterface

	==See Also==		==See Also==

← Older revision		Revision as of 09:45, 29 August 2013
Line 1:		Line 1:
	{{usermanualswebinterface}}		{{usermanualswebinterface}}

	~~Commit~~ Web Interface supports the ability to accept SSL connections (https rather than http).		CommitCRM Web Interface supports the ability to accept SSL connections (https rather than http).

	Using SSL with ~~Commit~~ Web Interface is OPTIONAL. You can use ~~Commit~~ Web Interface without setting up SSL.		Using SSL with CommitCRM Web Interface is OPTIONAL. You can use CommitCRM Web Interface without setting up SSL.

	The first step you should take if you want to use SSL with ~~Commit~~ Web Interface is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.		The first step you should take if you want to use SSL with CommitCRM Web Interface is to obtain SSL certificates from an authorized SSL authority such as Verisign or Thawte.

	If you'd like to read a SSL Certificate creation tutorial, [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]].		If you'd like to read a SSL Certificate creation tutorial, [[KB:_Creating_a_new_SSL_Certificate_for_the_Web_Interface\|please click here]].
Line 11:		Line 11:

	== Saving the Certificates Files ==		== Saving the Certificates Files ==
	~~Commit~~ requires that your certificates files be in the .pem file format.		CommitCRM requires that your certificates files be in the .pem file format.
	You should have three certificates files with the following names:		You should have three certificates files with the following names:

Line 18:		Line 18:
	Place your certificates files in the following folder:		Place your certificates files in the following folder:

	<Installation_DIR>\~~Commit~~\WebInterface		<Installation_DIR>\CommitCRM\WebInterface

	If your certificates are in another file format, convert them to the .pem file format.		If your certificates are in another file format, convert them to the .pem file format.
	Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.		Read the [[Using SSL with Web Interface#SSL Troubleshooting\|SSL Troubleshooting]] to see how to convert certain types of SSL certificate file formats.

	== Activating SSL with ~~Commit~~ ==		== Activating SSL with CommitCRM ==
	You need to instruct ~~Commit~~ Web Interface to use SSL. To do so, you must edit the following file:<br><Installation_DIR>\~~Commit~~\WebInterface\CommitWebInterface.ini		You need to instruct CommitCRM Web Interface to use SSL. To do so, you must edit the following file:<br><Installation_DIR>\CommitCRM\WebInterface\CommitWebInterface.ini

	Change the token settings in the above file to Yes as follows:<br>UseSSLEncryption=Y		Change the token settings in the above file to Yes as follows:<br>UseSSLEncryption=Y

	== Setting the SSL Port ==		== Setting the SSL Port ==
	The SSL communication between users/browsers and ~~Commit~~ Web Interface uses a dedicated port.		The SSL communication between users/browsers and CommitCRM Web Interface uses a dedicated port.

	Set a port number for ~~Commit~~ Web Interface. This port should not be in use by any other application or service.		Set a port number for CommitCRM Web Interface. This port should not be in use by any other application or service.

	We recommend using the ~~Commit~~ default port for SSL: 4962.		We recommend using the CommitCRM default port for SSL: 4962.

	If you decide to use another port, make sure that:		If you decide to use another port, make sure that:
Line 39:		Line 39:
	#You select a port value other than the standard SSL port (443) which is probably already in use on your server (by IIS for example).		#You select a port value other than the standard SSL port (443) which is probably already in use on your server (by IIS for example).

	To configure the SSL port, set the SSLPort token value in the following settings file:<br><Installation_DIR>\~~Commit~~\WebInterface\CommitWebInterface.ini		To configure the SSL port, set the SSLPort token value in the following settings file:<br><Installation_DIR>\CommitCRM\WebInterface\CommitWebInterface.ini

	<u>Important Note:</u><br>If you use a firewall, proxy, etc., it is recommended that you open Port 4962 in order to allow a connection to be established with ~~Commit~~ Web Interface.<br>If this port is blocked by a firewall, a connection cannot be established.		<u>Important Note:</u><br>If you use a firewall, proxy, etc., it is recommended that you open Port 4962 in order to allow a connection to be established with CommitCRM Web Interface.<br>If this port is blocked by a firewall, a connection cannot be established.

	== Setting SSL Certificate Password ==		== Setting SSL Certificate Password ==
	If you have a password for your SSL Certificate (SSL Certificate passwords are optional), enter the password for the SSlPassword token in:<br><Installation_DIR>\~~Commit~~\WebInterface\CommitWebInterface.ini		If you have a password for your SSL Certificate (SSL Certificate passwords are optional), enter the password for the SSlPassword token in:<br><Installation_DIR>\CommitCRM\WebInterface\CommitWebInterface.ini

	== Modifying the Login Page to Use SSL ==		== Modifying the Login Page to Use SSL ==
Line 72:		Line 72:

	*'''General Information'''		*'''General Information'''
	This issue is relevant only when you configure ~~Commit~~ Web Interface to use SSL. ~~Commit~~ requires that your certificate files all have the .pem format.		This issue is relevant only when you configure CommitCRM Web Interface to use SSL. CommitCRM requires that your certificate files all have the .pem format.

	If your certificates are in another format, convert them to the .pem format by following these instructions:		If your certificates are in another format, convert them to the .pem format by following these instructions:
Line 84:		Line 84:

	*'''Convert the exported .pfx file to a .pem format'''		*'''Convert the exported .pfx file to a .pem format'''
	To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from ~~Commit~~'s web site at the following URL:<br>http://www.CommitCRM.com/downloads/openssl.exe		To convert the .pfx file to a .pem file, you need to use a utility called openssl.exe.<br>The utility can be downloaded from CommitCRM's web site at the following URL:<br>http://www.CommitCRM.com/downloads/openssl.exe

	After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:		After downloading this file and saving it to your disk, open a command window and navigate to the folder where the utility is stored. Run the following command:
Line 115:		Line 115:
	The final stage is to obtain the Root.pem file.<br>This is the Certificate Authority certificate file. You can obtain this from Internet Explorer > Tools > Internet Options.<br>Navigate to the Content tab and click on Certificates.<br>In Trusted Root Certificate Authority tab, select the Authority that issued your certificate and the Export it in Base64 (cer) format.		The final stage is to obtain the Root.pem file.<br>This is the Certificate Authority certificate file. You can obtain this from Internet Explorer > Tools > Internet Options.<br>Navigate to the Content tab and click on Certificates.<br>In Trusted Root Certificate Authority tab, select the Authority that issued your certificate and the Export it in Base64 (cer) format.

	The exported file format is the SAME as the .pem format, so after exporting it simply rename the file Root.pem and save it with the other certificate file in folder<br><Installation_DIR>\~~Commit~~\WebInterface		The exported file format is the SAME as the .pem format, so after exporting it simply rename the file Root.pem and save it with the other certificate file in folder<br><Installation_DIR>\CommitCRM\WebInterface

	==See Also==		==See Also==