OAuth Setup - Revision history

Dgreenwood at 15:30, 19 September 2025

2025-09-19T15:30:50Z

← Older revision		Revision as of 10:30, 19 September 2025
Line 1:		Line 1:
	{\|class="~~attn~~-box"		{\|class="fyi-box"
	\|		\|
	~~⚠~~		FYI
	\|		\|
	'''''Looking for OAuth Service Login setup for Exchange connections? You're in the wrong place.'''''		'''''Looking for OAuth Service Login setup for Exchange connections? You're in the wrong place.'''''

Dgreenwood at 15:21, 19 September 2025

2025-09-19T15:21:42Z

← Older revision		Revision as of 10:21, 19 September 2025
Line 1:		Line 1:
			{\|class="attn-box"
			\|
			⚠
			\|
			'''''Looking for OAuth Service Login setup for Exchange connections? You're in the wrong place.'''''

			This article is about setting up OAuth for the Grooper and GWS websites, not setting up Exchange CMIS Connections to use the OAuth client credentials flow. For information on setting up OAuth for Exchange connections, visit the [[Exchange#OAuth Service Login setup\|OAuth Service Login setup portion in the Exchange article]].
			\|}

	[[File:2025 OAuth 01 login.png\|frame\|right\|Login with your Microsoft credentials with OAuth]]		[[File:2025 OAuth 01 login.png\|frame\|right\|Login with your Microsoft credentials with OAuth]]

Dgreenwood at 14:22, 16 September 2025

2025-09-16T14:22:29Z

← Older revision		Revision as of 09:22, 16 September 2025
Line 15:		Line 15:
	* Simplified logins - Users can log into multiple applications with existing accounts. In the case of Grooper, with a Microsoft Entra ID account (formerly Azure Active Directory).		* Simplified logins - Users can log into multiple applications with existing accounts. In the case of Grooper, with a Microsoft Entra ID account (formerly Azure Active Directory).
	* Integrations - OAuth is the security standard for app-to-app communication. Securing Grooper with OAuth allows us new integration options, including using Azure Bot Services to extend AI Assistants to external chat channels.		* Integrations - OAuth is the security standard for app-to-app communication. Securing Grooper with OAuth allows us new integration options, including using Azure Bot Services to extend AI Assistants to external chat channels.

			{\|class="attn-box"
			\|
			⚠
			\|
			'''''IMPORTANT! OAuth settings must be configured every time a new Grooper Web Client build is installed.'''''

			OAuth settings are stored configured in the Grooper and GWS websites' web.config files. These files are erased and regenerated every time the Grooper Web Client installer runs. Please back up these settings before running the Grooper Web Client installer. You will need to re-enter them every time you install the Grooper Web Client.
			\|}

	=== Basic steps ===		=== Basic steps ===

Dgreenwood: /* Configuring OAuth for GWS */

2025-07-18T20:48:43Z

Configuring OAuth for GWS

@@ Line 145: / Line 145: @@
 # Select "bot:ClientId:1". For "value" in the Properties panel, you will enter an Azure bot's "Microsoft App ID".
 #*<li class="fyi-bullet"> Multiple Azure Bot resources can be added using the format "bot:ClientId:2", "bot:ClientId:3", etc.
 # Close the Collection Editor.
 # In the "Actions" panel, select "Apply".
 # Restart the Grooper app pool (In the Connections panel, select "Application Pools". Select "GrooperAppPool" from the list. In the Actions panel, select "Recycle").

Dgreenwood: Dgreenwood moved page OAuth to OAuth Setup

2025-07-18T20:17:47Z

Dgreenwood moved page OAuth to OAuth Setup

← Older revision	Revision as of 15:17, 18 July 2025
(No difference)

Dgreenwood: /* Configuring OAuth for GWS */

2025-07-18T20:14:26Z

Configuring OAuth for GWS

@@ Line 130: / Line 130: @@
 <big>Configuration steps:</big>
 *<li class="attn-bullet" style="margin-bottom:1em> '''''BE AWARE!''''' You will need to do this '''every time you install Grooper Web Client''', including when you install new minor builds. Installing Grooper Web Client will wipe clean all previous settings entered in the website's configuration file.
 <!--

Dgreenwood at 19:02, 18 July 2025

2025-07-18T19:02:04Z

← Older revision		Revision as of 14:02, 18 July 2025
Line 12:		Line 12:

	Benefits to OAuth:		Benefits to OAuth:
	* Security - Users do not have to share their passwords with third party applications.		* Security - Users do not have to share their passwords with third party applications. Microsoft Entra ID supports multifactor authentication as well.
	* Simplified logins - Users can log into multiple applications with existing accounts. In the case of Grooper, with a Microsoft Entra ID account (formerly Azure Active Directory).		* Simplified logins - Users can log into multiple applications with existing accounts. In the case of Grooper, with a Microsoft Entra ID account (formerly Azure Active Directory).
	* Integrations - OAuth is the security standard for app-to-app communication. Securing Grooper with OAuth allows us new integration options, including using Azure Bot Services to extend AI Assistants to external chat channels.		* Integrations - OAuth is the security standard for app-to-app communication. Securing Grooper with OAuth allows us new integration options, including using Azure Bot Services to extend AI Assistants to external chat channels.

Dgreenwood: /* Configuring OAuth for Grooper app users */

2025-07-18T18:59:36Z

Configuring OAuth for Grooper app users

← Older revision		Revision as of 13:59, 18 July 2025
Line 112:		Line 112:
	# In the "Actions" panel, select "Apply".		# In the "Actions" panel, select "Apply".
	# Restart the Grooper app pool (In the Connections panel, select "Application Pools". Select "GrooperAppPool" from the list. In the Actions panel, select "Recycle").		# Restart the Grooper app pool (In the Connections panel, select "Application Pools". Select "GrooperAppPool" from the list. In the Actions panel, select "Recycle").

			<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/cmd7qshqn000z130ino4m3g5t?embed_v=2" loading="lazy" title="2025Wiki - OAuth - Configuring OAuth for Grooper app users" allow="clipboard-write" frameborder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>

	=== Configuring OAuth for GWS ===		=== Configuring OAuth for GWS ===

Dgreenwood at 18:47, 18 July 2025

2025-07-18T18:47:30Z

← Older revision		Revision as of 13:47, 18 July 2025
Line 22:		Line 22:
	To do this you will:		To do this you will:

	(1) Create ~~an Azure~~ Entra ID app registration for Grooper		(1) Create a Microsoft Entra ID app registration for Grooper
	:* An "app registration" registers an external application with Entra ID (formerly Azure Active Directory).		:* An "app registration" registers an external application with Entra ID (formerly Azure Active Directory).
	:* This gives identity to applications (like Grooper) in an organization's domain/tenant.		:* This gives identity to applications (like Grooper) in an organization's domain/tenant.
Line 31:		Line 31:
	=== Registering an app in Entra ID for Grooper ===		=== Registering an app in Entra ID for Grooper ===

	Whether configuring OAuth for the Grooper website or the GWS website, your first step is making an app registration for Grooper in ~~Azure~~ Entra ID (formerly Azure Active Directory). This registration will identify Grooper as a trusted application within your tenant and allow Entra ID users access when opening the Grooper application and allow app-to-app communication for GWS API endpoints.		Whether configuring OAuth for the Grooper website or the GWS website, your first step is making an app registration for Grooper in Microsoft Entra ID (formerly Azure Active Directory). This registration will identify Grooper as a trusted application within your tenant and allow Entra ID users access when opening the Grooper application and allow app-to-app communication for GWS API endpoints.

	<big>Create the app registration</big>		<big>Create the app registration</big>

Dgreenwood: /* Registering an app in Entra ID for Grooper */

2025-07-17T19:22:41Z

Registering an app in Entra ID for Grooper

← Older revision		Revision as of 14:22, 17 July 2025
Line 42:		Line 42:
	# Configure the Redirect URI" (You will need this later).		# Configure the Redirect URI" (You will need this later).
	#* Select "Web" for the platform type.		#* Select "Web" for the platform type.
	#* The URI will follow this format: <code><nowiki>https://{~~domainURI~~}/Grooper/Auth/Callback</nowiki></code>		#* The URI will follow this format: <code><nowiki>https://{webserver-name-or-domain-name}/Grooper/Auth/Callback</nowiki></code>
	#*<li class="fyi-bullet"> If you forget to do this, you can add a redirect URI later. However, it will be needed when configuring the Grooper web server.		#*<li class="fyi-bullet"> If you forget to do this, you can add a redirect URI later. However, it will be needed when configuring the Grooper web server.
	# Press the "Register" button to register the app.		# Press the "Register" button to register the app.