Install and Setup - Revision history

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-15T13:34:32Z

SSL and HTTPS: Secure website connections

← Older revision		Revision as of 08:34, 15 April 2026
Line 282:		Line 282:

	*'''Effective as of Grooper 25.0.0043''', the application enforces HTTPS for all installations and access.		*'''Effective as of Grooper 25.0.0043''', the application enforces HTTPS for all installations and access.
	* HTTPS is now mandatory. A trusted certificate must be ~~in place prior to installation~~ or ~~upgrade~~, or the application will not function.		* HTTPS is now mandatory. A trusted TLS/SSL certificate must be configured before installing or upgrading, or the application will not function.
	* '''Impact'''		* '''Impact'''
	** Opening the Grooper web app over HTTP will fail.		** Opening the Grooper web app over HTTP will fail.
Line 291:		Line 291:
	* '''Supported Certificate Options'''		* '''Supported Certificate Options'''
	*# Self-Signed Certificate		*# Self-Signed Certificate
	# Suitable for ~~development and testing~~ environments		# Suitable for dev/test environments only — requires manual trust installation on each client machine.
	# Requires manual trust installation on each client
	# Will otherwise trigger browser security warnings		# Will otherwise trigger browser security warnings
	*# Internal Certificate Authority (~~Most~~ typical)		*# Internal Certificate Authority (most typical)
	# Most organizations will use an internally issued certificate managed by their IT.		# Most organizations will use an internally issued certificate managed by their IT.
	# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)		# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)
Line 305:		Line 304:
	# Necessary only for internet-facing deployments		# Necessary only for internet-facing deployments
	# Requires a valid public domain		# Requires a valid public domain
	# Examples ~~include~~:		# Examples: [https://en.wikipedia.org/wiki/DigiCert DigiCert], [https://en.wikipedia.org/wiki/GlobalSign GlobalSign],[https://en.wikipedia.org/wiki/Let%27s_Encrypt Let's Encrypt]
	~~#*~~ [https://en.wikipedia.org/wiki/DigiCert DigiCert]
	~~#*~~ [https://en.wikipedia.org/wiki/GlobalSign GlobalSign]
	~~#*~~ [https://en.wikipedia.org/wiki/Let%27s_Encrypt Let's Encrypt]

	Below, we will instruct you how to create a self-signed certificate and set up your browser to trust the certificate. This is the quickest way to get started testing a Grooper install.		Below, we will instruct you how to create a self-signed certificate and set up your browser to trust the certificate. This is the quickest way to get started testing a Grooper install.

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-15T12:56:09Z

SSL and HTTPS: Secure website connections

← Older revision		Revision as of 07:56, 15 April 2026
Line 303:		Line 303:
	*# Public Certificate Authority		*# Public Certificate Authority
	# Trusted by all browsers and devices		# Trusted by all browsers and devices
	# ~~Recommended~~ for internet-facing deployments		# Necessary only for internet-facing deployments
	# Requires a valid public domain		# Requires a valid public domain
	# Examples include:		# Examples include:

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-15T12:55:38Z

SSL and HTTPS: Secure website connections

← Older revision		Revision as of 07:55, 15 April 2026
Line 288:		Line 288:
	** Clients will be unable to access the application unless the server presents a trusted TLS/SSL certificate.		** Clients will be unable to access the application unless the server presents a trusted TLS/SSL certificate.
	* '''Required Action'''		* '''Required Action'''
	** Before installing or upgrading, configure the ~~application~~ server with a valid HTTPS certificate that is trusted by all client machines.		** Before installing or upgrading, configure the Grooper web server with a valid HTTPS certificate that is trusted by all client machines.
	* '''Supported Certificate Options'''		* '''Supported Certificate Options'''
	*# Self-Signed Certificate		*# Self-Signed Certificate

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-15T12:54:58Z

SSL and HTTPS: Secure website connections

← Older revision		Revision as of 07:54, 15 April 2026
Line 294:		Line 294:
	# Requires manual trust installation on each client		# Requires manual trust installation on each client
	# Will otherwise trigger browser security warnings		# Will otherwise trigger browser security warnings
	*# Internal Certificate Authority (~~Recommended~~)		*# Internal Certificate Authority (Most typical)
	# Most organizations will use an internally issued certificate managed by their IT.		# Most organizations will use an internally issued certificate managed by their IT.
	# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)		# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-13T16:22:47Z

SSL and HTTPS: Secure website connections

← Older revision		Revision as of 11:22, 13 April 2026
Line 281:		Line 281:
	<big>Breaking Change: HTTPS Required for Application Installation</big>		<big>Breaking Change: HTTPS Required for Application Installation</big>

	*'''Effective as of Grooper 25.0.~~0044~~''', the application enforces HTTPS for all installations and access.		*'''Effective as of Grooper 25.0.0043''', the application enforces HTTPS for all installations and access.
	* HTTPS is now mandatory. A trusted certificate must be in place prior to installation or upgrade, or the application will not function.		* HTTPS is now mandatory. A trusted certificate must be in place prior to installation or upgrade, or the application will not function.
	* '''Impact'''		* '''Impact'''

Dgreenwood: /* SSL and HTTPS: Secure website connections */

2026-04-13T15:48:12Z

SSL and HTTPS: Secure website connections

@@ Line 275: / Line 275: @@
 * Always use HTTPS to connect to the Grooper web app.
 * NEVER use HTTP to connect to the Grooper web app. Scanned images will be refused if using an HTTP address.
-* A self-signed certificate on the Grooper web server should be sufficient for scenarios where Grooper is isolated to your own network.
+* '''At minimum''' a [[Install_and_Setup#How to create and bind a self-signed certificate|self-signed certificate]] must be installed on the Grooper web server. ''This is generally acceptable for test environments.''
-* For information on how to create and bind a self-signed certificate, [[Install_and_Setup#How to create and bind a self-signed certificate|review this part of the Install and Setup article.]]
+* '''Best practice:''' Use an internally issued certificate managed by your organization's IT.
 |}
-To connect to a website with a secure connection (HTTPS), you have the following options:
+<big>Breaking Change: HTTPS Required for Application Installation</big>
-We will instruct you how to do option 2.  Keep reading to learn how to create a self-signed certificate and set up your browser to trust the certificate.
+Below, we will instruct you how to create a self-signed certificate and set up your browser to trust the certificate. This is the quickest way to get started testing a Grooper install.
 <div style="padding-left: 1.5em;">
 ===== How to create and bind a self-signed certificate =====

Dgreenwood at 22:44, 24 February 2026

2026-02-24T22:44:22Z

← Older revision		Revision as of 17:44, 24 February 2026
Line 61:		Line 61:
	=== Downloading Grooper installers ===		=== Downloading Grooper installers ===

	# If you have not registered at Grooper xChange, do so by ~~clicking~~ the ~~link below.~~		# If you have not registered at Grooper xChange, do so by going to the [https://grooper.com/category/xchange/ Grooper xChange website] and clicking the "Register" link.
	#:https://~~xchange.~~grooper.com/~~entry~~/~~register~~		# Log into [https://grooper.com/category/xchange/ Grooper xChange].
	# Log into ~~Grooper xChange at http~~://~~xchange.~~grooper.com.		# Go to the the "[https://grooper.com/category/xchange/downloads/ Downloads and Resources]" section.
	# Go to the the "[https://~~www.bisok~~.com/~~grooper-~~xchange/downloads~~-and-resources~~/ Downloads and Resources]" section.
	# The current support versions of Grooper are listed at the top. Click the link for the version you wish to install.		# The current support versions of Grooper are listed at the top. Click the link for the version you wish to install.
	# On the installers page you will see three links to downloads:		# On the installers page you will see three links to downloads:

Dgreenwood: /* Option 2: Create a self-signed cert from PowerShell */

2026-02-18T14:54:47Z

Option 2: Create a self-signed cert from PowerShell

← Older revision		Revision as of 09:54, 18 February 2026
Line 356:		Line 356:
	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84wmybv00arxq0hpn4yo1c9?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 06 Create a self-signed certificate (PowerShell)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84wmybv00arxq0hpn4yo1c9?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 06 Create a self-signed certificate (PowerShell)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	~~<big>~~How to add the cert to a browsers trusted root certification authority store (from Chrome)~~</big>~~		===== How to add the cert to a browsers trusted root certification authority store (from Chrome) =====

	With the self-signed cert created and bound, you will be able to navigate to the Grooper website (<nowiki>https://yourServerName/Grooper</nowiki>). However, your browser will warn you the connection is not secure. You now have two options:		With the self-signed cert created and bound, you will be able to navigate to the Grooper website (<nowiki>https://yourServerName/Grooper</nowiki>). However, your browser will warn you the connection is not secure. You now have two options:

Dgreenwood: /* How to create and bind a self-signed certificate */

2026-02-18T14:53:48Z

How to create and bind a self-signed certificate

← Older revision		Revision as of 09:53, 18 February 2026
Line 313:		Line 313:
	Here, we will cover the ''most basic'' steps to create a self-signed SSL certificate and bind it to the Grooper Web Client's website.		Here, we will cover the ''most basic'' steps to create a self-signed SSL certificate and bind it to the Grooper Web Client's website.
	<div style="padding-left: 1.5em;">		<div style="padding-left: 1.5em;">
	~~<big>~~Option 1: Create a self-signed cert in IIS~~</big>~~		===== Option 1: Create a self-signed cert in IIS =====

	# Open the "Information Internet Services (IIS) Manager" application on your web server.		# Open the "Information Internet Services (IIS) Manager" application on your web server.
Line 333:		Line 333:
	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84uca6y02po3h0igp7mg3lk?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 05 Create a self-signed certificate (IIS)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84uca6y02po3h0igp7mg3lk?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 05 Create a self-signed certificate (IIS)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	~~<big>~~Option 2: Create a self-signed cert from PowerShell~~</big>~~		=====Option 2: Create a self-signed cert from PowerShell=====

	Some organizations have reported issues with how IIS creates a self-signed cert. If you attempt to open the Grooper website and run into an error message that says "ERR_SSL_KEY_USAGE_INCOMPATIBLE", this method should resolve your issue.		Some organizations have reported issues with how IIS creates a self-signed cert. If you attempt to open the Grooper website and run into an error message that says "ERR_SSL_KEY_USAGE_INCOMPATIBLE", this method should resolve your issue.

Dgreenwood: /* HTTP WORKAROUND: How to treat a website as secure READ WITH CAUTION! */

2026-02-18T14:30:37Z

HTTP WORKAROUND: How to treat a website as secure READ WITH CAUTION!

← Older revision		Revision as of 09:30, 18 February 2026
Line 388:		Line 388:
	<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84yzxv4006wz50ho2w5lacy?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 07 Trust the cert from a browser (Chrome)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>		<div style="position: relative; box-sizing: content-box; max-height: 80vh; max-height: 80svh; width: 100%; aspect-ratio: 1.7777777777777777; padding: 40px 0 40px 0;"><iframe src="https://app.supademo.com/embed/cm84yzxv4006wz50ho2w5lacy?embed_v=2" loading="lazy" title="2025Wiki - Install and Setup - 07 Trust the cert from a browser (Chrome)" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
	</div>		</div>
			<!--- EDITORS NOTE: I am commenting out this section to hide this from public view. Since the PowerShell SSL method works reliably, I believe it is ill advised to inform users how to do this. Documentation still remains viewable to wiki editors for reference.
	===== HTTP WORKAROUND: How to treat a website as secure READ WITH CAUTION! =====		===== HTTP WORKAROUND: How to treat a website as secure READ WITH CAUTION! =====

Line 405:		Line 406:

	With the flag added, the Grooper web client will behave as if you're connecting with HTTPS even though you're connecting with HTTP.		With the flag added, the Grooper web client will behave as if you're connecting with HTTPS even though you're connecting with HTTP.
			--->
	</div>		</div>
	</div>		</div>

← Older revision		Revision as of 07:56, 15 April 2026
Line 303:		Line 303:
	*# Public Certificate Authority		*# Public Certificate Authority
	# Trusted by all browsers and devices		# Trusted by all browsers and devices
	# ~~Recommended~~ for internet-facing deployments		# Necessary only for internet-facing deployments
	# Requires a valid public domain		# Requires a valid public domain
	# Examples include:		# Examples include:

← Older revision		Revision as of 07:54, 15 April 2026
Line 294:		Line 294:
	# Requires manual trust installation on each client		# Requires manual trust installation on each client
	# Will otherwise trigger browser security warnings		# Will otherwise trigger browser security warnings
	*# Internal Certificate Authority (~~Recommended~~)		*# Internal Certificate Authority (Most typical)
	# Most organizations will use an internally issued certificate managed by their IT.		# Most organizations will use an internally issued certificate managed by their IT.
	# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)		# Issued by your organization’s internal PKI (e.g., Active Directory Certificate Services)