OAuth Client Credentials

Implements OAuth 2.0 Client Credentials authentication for secure service-to-service HTTP integration in Grooper.

Remarks

The OAuth Client Credentials class enables Grooper to authenticate with external APIs and services 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 from an authorization server using its client ID and client secret.

Overview

Use OAuth Client Credentials when integrating with APIs that require application-level authentication, such as Microsoft Graph, Azure, or other enterprise services. This flow does not involve user interaction; instead, Grooper presents its credentials to the authorization server and receives an access token for API requests.

Usage

• Set the 'Token Endpoint URL', 'Client ID', and 'Client Secret' properties to the values provided by your authorization server.
• Optionally, specify the 'Scope' property to request specific permissions for the access token.
• When Grooper makes an HTTP request, it automatically obtains and caches an access token, then sends it as Authorization: Bearer <token>.
• This method is suitable for backend integrations, automation, and scenarios where no user is present.

Security Notes

• The client secret is sensitive and should be protected. It is stored securely and only used for token acquisition.
• Always use HTTPS for all communication with the token endpoint and API.
• Do not share client credentials with untrusted parties or expose them in logs.

Example

To authenticate with an OAuth 2.0 provider:

Token Endpoint URL: https://login.example.com/oauth2/v2.0/token Client ID: 12345678-90ab-cdef-1234-567890abcdef Client Secret: (your secret) Scope: https://api.example.com/.default

The resulting HTTP header will be:

Authorization: Bearer <access_token>

Properties

Name	Type		Description
Url	String	►	The URL of the authorization server's token endpoint. Requiredtrue Enter the full URL of the OAuth 2.0 token endpoint provided by your authorization server. This is where Grooper will send its client credentials to obtain an access token. The URL is typically provided in your API or identity provider's documentation. Always use an HTTPS endpoint to protect credentials in transit. Example: https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token
Client Id	String	►	The client application's identifier issued by the authorization server. Requiredtrue Enter the client ID assigned to your application during registration with the authorization server. This value uniquely identifies Grooper as an application when requesting tokens. The client ID is not secret, but must match the value registered with your API provider.
Client Secret	String	►	The client application's secret key for authentication. Requiredtrue Enter the client secret associated with your client ID. This value is used to prove Grooper's identity to the authorization server. The client secret is sensitive and should be protected. It is stored securely and only used for token acquisition. Never share this value or expose it in logs or user interfaces.
Scope	String	►	A space-separated list of permissions or scopes to request for the access token. Specify the scopes required for your integration, as defined by the API provider. Scopes control what the access token allows Grooper to do. If omitted, the token may be granted with default permissions. Consult your API documentation for required scopes. Example: https://graph.microsoft.com/.default

Context Menu Commands

Command	Shortcut	Description
~/Resource/GetIcon?typeName=blank Test		Tests the process of obtaining an OAuth 2.0 access token using the configured client credentials.

Used By

Web Service