OAuth Service Login

Implements OAuth 2.0 authentication using the client credentials flow for secure server-to-server access in Grooper.

Remarks

OAuth Service Login enables Grooper to authenticate with external content platforms and APIs using the OAuth 2.0 Client Credentials Flow. This method is designed for server-to-server scenarios, where Grooper acts as an application (not a user) and obtains an access token directly from the authorization server using its client ID and client secret.

Overview

When OAuth Service Login is selected as the authentication method for a CMIS Binding or Custom Binding, Grooper sends a request to the authorization server's token endpoint, providing the configured client credentials and requested scopes. The server responds with an access token, which Grooper uses to authenticate HTTP requests to the target API or service.

This method is ideal for backend integrations, automation, and other scenarios where user interaction is not possible or required. It is commonly used with APIs that support machine-to-machine authentication, such as Microsoft Graph, Azure services, and other enterprise platforms.

Usage Notes

• Configure the 'Url', 'Client Id', and 'Client Secret' properties with the values provided by your authorization server or identity provider.
• The 'Scope' property allows you to specify the permissions the application is requesting. This may be required or optional, depending on the server.
• No user interaction is required; tokens are obtained and refreshed automatically as needed.
• Ensure that the client credentials are kept secure, as they grant access to the configured resources.

After configuration, Grooper will use the provided credentials to obtain access tokens for all HTTP requests made by the binding.

Properties

Name	Type		Description
Url	String	►	The URL of the authorization server's token endpoint. Requiredtrue The 'Url' property specifies the endpoint where Grooper will request access tokens using the OAuth client credentials flow. This is typically provided by your identity provider or API platform (for example, https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token). Ensure that the URL is correct and accessible from the Grooper environment. An incorrect or unreachable URL will prevent authentication and access to the target API.
Client Id	String	►	The client application's identifier, which was issued to the client during the client registration process with the authorization server. Requiredtrue The 'Client Id' property specifies the unique identifier assigned to your application by the authorization server. This value is required for all OAuth client credentials flows and is used to identify the application when requesting tokens. Obtain the client ID from your identity provider's application registration portal. Enter it exactly as provided.
Client Secret	String	►	The client application's secret key, used for authentication of the client application. Requiredtrue The 'Client Secret' property specifies the secret key associated with your application's client ID. This value is used to prove the application's identity to the authorization server and must be kept confidential. Enter the client secret exactly as provided by your identity provider. If the secret is rotated or changed, update this property in Grooper to maintain connectivity.
Scope	String	►	A space-separated list of permissions or scopes that the client is requesting for the access token. The 'Scope' property allows you to specify the permissions or access levels the application is requesting from the authorization server. The required format and values depend on the API or service being accessed (for example, https://api.example.com/.default or openid profile email). This property is optional for some providers. If omitted, the token may be granted with the default scope. Consult your provider's documentation for the correct values and usage.

Used By

ExchangeSharePointWeb Service Lookup