Setting up HTTPS - Revision history

Arvind: /* Error while binding COMODO signed certificate to NEOSYS website */

2019-02-04T10:15:44Z

Error while binding COMODO signed certificate to NEOSYS website

← Older revision		Revision as of 10:15, 4 February 2019
Line 66:		Line 66:
	A specified logon session does not exist. It may already have been terminated.		A specified logon session does not exist. It may already have been terminated.

	If importing a certificate ONCE at the top level onto a NEOSYS controlled server with multiple web sites then you need to ~~have used~~ the ~~you need~~ to "~~mark~~ the ~~private key as exportable"~~.		If importing a certificate ONCE at the top level onto a NEOSYS controlled server with multiple web sites then you need to mark the "Allow this key to be exported" checkbox when importing the certificate to IIS.

Gregory: /* Creating a single HTTPS web site on Windows 2008 */

2018-10-29T12:42:11Z

Creating a single HTTPS web site on Windows 2008

← Older revision		Revision as of 12:42, 29 October 2018
Line 13:		Line 13:
	To create a single HTTPS web site on Windows 2008, follow three simple steps:		To create a single HTTPS web site on Windows 2008, follow three simple steps:

	Copy the ".hosts.neosys.com.pfx" certificate saved in d:\hosts\certificates on win3 to the server (password to be used is present in a text file in the same folder).		#Copy the "*.hosts.neosys.com.pfx" certificate saved in d:\hosts\certificates on win3 to the server (password to be used is present in a text file in the same folder).
	*Import the certificate to IIS without option to export and MUST be deleted after import. See [http://techwiki.neosys.com/index.php/Setting_up_HTTPS#Steps_to_follow_while_importing_certificate_and_why Importing certificate in IIS] for details.		#Import the certificate to IIS without option to export and MUST be deleted after import. See [http://techwiki.neosys.com/index.php/Setting_up_HTTPS#Steps_to_follow_while_importing_certificate_and_why Importing certificate in IIS] for details.
	*Click on Sites > Client Web Site > Bindings. In the Bindings section - click on Add and select https, All Unassigned IP addresses, port 4430 and select the certificate from the drop down and click OK.		#Click on Sites > Client Web Site > Bindings. In the Bindings section - click on Add and select https, All Unassigned IP addresses, port 4430 and select the certificate from the drop down and click OK.

	[[image:sslwin2008-2.jpg]]		[[image:sslwin2008-2.jpg]]

Steve at 17:17, 6 October 2018

2018-10-06T17:17:05Z

← Older revision		Revision as of 17:17, 6 October 2018
Line 1:		Line 1:
	== Setting up HTTPS for NEOSYS website ==		== Setting up HTTPS for NEOSYS website ==

			CAUTION: When importing certificates on servers that are not owned by NEOSYS you MUST NOT check the "allow certificate export" option otherwise anybody with access to the server can steal the NEOSYS certificate and pass off their own servers as NEOSYS certified.

	NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.		NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.

Steve: /* Error while binding COMODO signed certificate to NEOSYS website */

2018-10-06T17:11:22Z

Error while binding COMODO signed certificate to NEOSYS website

← Older revision		Revision as of 17:11, 6 October 2018
Line 64:		Line 64:
	A specified logon session does not exist. It may already have been terminated.		A specified logon session does not exist. It may already have been terminated.

	~~You can fix this error by~~ importing the ~~certificate using~~ the ~~MMC (Microsoft Management Console) instead of directly doing it from IIS.~~		If importing a certificate ONCE at the top level onto a NEOSYS controlled server with multiple web sites then you need to have used the you need to "mark the private key as exportable".

	~~Follow~~ the ~~link for instructions:~~
	~~http://support.microsoft~~.~~com/kb/232137~~

Arya: /* Error while binding COMODO signed certificate to NEOSYS website */

2017-04-11T10:56:15Z

Error while binding COMODO signed certificate to NEOSYS website

← Older revision		Revision as of 10:56, 11 April 2017
Line 61:		Line 61:

	[[image:Test11.jpg]]		[[image:Test11.jpg]]

			A specified logon session does not exist. It may already have been terminated.

	You can fix this error by importing the certificate using the MMC (Microsoft Management Console) instead of directly doing it from IIS.		You can fix this error by importing the certificate using the MMC (Microsoft Management Console) instead of directly doing it from IIS.

Arvind: /* Setting up HTTPS for installations where outside office access is usually restricted */

2016-12-04T12:40:38Z

Setting up HTTPS for installations where outside office access is usually restricted

← Older revision		Revision as of 12:40, 4 December 2016
Line 50:		Line 50:
	==Setting up HTTPS for installations where outside office access is usually restricted==		==Setting up HTTPS for installations where outside office access is usually restricted==

	~~To access NEOSYS via HTTPS, port 4430 must be open on the router and on the server and https binding with SSL certificate.~~ During a new installation, ~~on neosys~~ support ~~computer~~, ~~staff must check~~ if NEOSYS can be accessed via https ~~as user neosys and as a non-neosys user~~. Since management has informed that outside access~~(https)~~ is not ~~allowed~~, port 4430 ~~on server must be closed~~ and ~~binding to~~ https ~~must~~ be ~~removed. Do not close~~ port 4430 on router~~. This is done~~ to ~~quickly give clients outside access if requested~~ for ~~in future. Setting up port forwarding on router can be time consuming, clients will appreciate if quick support is provided~~.		During a new installation, support staff MUST import the certificate to IIS, bind the certificate to NEOSYS website (following the steps mentioned above in [[Setting_up_HTTPS#Creating_a_single_HTTPS_web_site_on_Windows_2008\|Creating a single HTTPS web site]]) and test if NEOSYS can be accessed via https on the server (https://localhost:4430), so that no problems are faced in future if the client ever requests for outside access with their management's approval.

			Since the client management has informed that outside access is not required, close the server's port 4430 (i.e. remove 4430 from Windows Firewall exceptions). Do not remove the certificate binding in IIS.

			If and when https access is required by the client, this can be enabled by unblocking the server's port 4430 and instructing the client to get their IT to configure the router to port forward port 4430 for https.

	== Troubleshooting setup of multiple HTTPS websites ==		== Troubleshooting setup of multiple HTTPS websites ==

Arvind: /* Setting up HTTPS for installations with more than 1 database */

2016-11-30T07:37:05Z

Setting up HTTPS for installations with more than 1 database

← Older revision		Revision as of 07:37, 30 November 2016
Line 46:		Line 46:
	==Setting up HTTPS for installations with more than 1 database==		==Setting up HTTPS for installations with more than 1 database==

	In cases where there are multiple databases within the same installation, you can use the same website to access all the databases. In case the Client asks for separate domain names for multiple databases, use the same steps as explained in [~~http://techwiki.neosys.com/index.php/~~Setting_up_HTTPS#Setting_up_HTTPS_for_NEOSYS_website Setting up HTTPS] as the case maybe.		In cases where there are multiple databases within the same installation, you can use the same website to access all the databases. In case the Client asks for separate domain names for multiple databases, use the same steps as explained in [[Setting_up_HTTPS#Setting_up_HTTPS_for_NEOSYS_website\|Setting up HTTPS]] as the case maybe.

	==Setting up HTTPS for installations where outside office access is usually restricted==		==Setting up HTTPS for installations where outside office access is usually restricted==

Priyanka: /* Setting up HTTPS for installations with more than 1 database */

2016-11-30T07:34:44Z

Setting up HTTPS for installations with more than 1 database

← Older revision		Revision as of 07:34, 30 November 2016
Line 47:		Line 47:

	In cases where there are multiple databases within the same installation, you can use the same website to access all the databases. In case the Client asks for separate domain names for multiple databases, use the same steps as explained in [http://techwiki.neosys.com/index.php/Setting_up_HTTPS#Setting_up_HTTPS_for_NEOSYS_website Setting up HTTPS] as the case maybe.		In cases where there are multiple databases within the same installation, you can use the same website to access all the databases. In case the Client asks for separate domain names for multiple databases, use the same steps as explained in [http://techwiki.neosys.com/index.php/Setting_up_HTTPS#Setting_up_HTTPS_for_NEOSYS_website Setting up HTTPS] as the case maybe.

			==Setting up HTTPS for installations where outside office access is usually restricted==

			To access NEOSYS via HTTPS, port 4430 must be open on the router and on the server and https binding with SSL certificate. During a new installation, on neosys support computer, staff must check if NEOSYS can be accessed via https as user neosys and as a non-neosys user. Since management has informed that outside access(https) is not allowed, port 4430 on server must be closed and binding to https must be removed. Do not close port 4430 on router. This is done to quickly give clients outside access if requested for in future. Setting up port forwarding on router can be time consuming, clients will appreciate if quick support is provided.

	== Troubleshooting setup of multiple HTTPS websites ==		== Troubleshooting setup of multiple HTTPS websites ==

Arvind: /* Setting up HTTPS for NEOSYS website */

2016-11-29T10:51:23Z

Setting up HTTPS for NEOSYS website

← Older revision		Revision as of 10:51, 29 November 2016
Line 3:		Line 3:
	NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.		NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.

	Pre prepared certificate for *.hosts.neosys.com web sites is present on the nl10r/win3 server. The certificate is signed by COMODO and supports SHA2 security algorithm. It is portable, ensures authenticity and is widely supported. Also refer to: http://itwiki.neosys.com/index.php/SSL_certificate		Pre prepared certificate for *.hosts.neosys.com web sites is present on the nl10r/win3 server. The certificate is signed by COMODO and supports SHA2 security algorithm. It is portable, ensures authenticity and is widely supported. Also refer to [http://itwiki.neosys.com/index.php/SSL_certificate SSL certificate]

	If a client's URL is not as per NEOSYS standards, but has been in use for many years, do not change the URL without a good enough reason.		If a client's URL is not as per NEOSYS standards, but has been in use for many years, do not change the URL without a good enough reason.

Priyanka: /* Setting up HTTPS for NEOSYS website */

2016-11-29T07:20:39Z

Setting up HTTPS for NEOSYS website

← Older revision		Revision as of 07:20, 29 November 2016
Line 3:		Line 3:
	NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.		NEOSYS has a very simple way of enabling https for all the clients. Every client has been set up with domain name " .hosts.neosys.com " where "" is the clientname.

	Pre prepared certificate for *.hosts.neosys.com web sites is present on the nl10r/win3 server. The certificate is signed by COMODO and supports SHA2 security algorithm. It is portable, ensures authenticity and is widely supported.		Pre prepared certificate for *.hosts.neosys.com web sites is present on the nl10r/win3 server. The certificate is signed by COMODO and supports SHA2 security algorithm. It is portable, ensures authenticity and is widely supported. Also refer to: http://itwiki.neosys.com/index.php/SSL_certificate

	If a client's URL is not as per NEOSYS standards, but has been in use for many years, do not change the URL without a good enough reason.		If a client's URL is not as per NEOSYS standards, but has been in use for many years, do not change the URL without a good enough reason.