HTTP Authentication Method

Defines how an HTTP client authenticates with an HTTP server when connecting to external content platforms in Grooper.

Remarks

HTTP Authentication Method provides the foundation for configuring authentication schemes used by Grooper's HTTP-based integrations, such as custom CMIS+ bindings and other external repository connections. This abstract class is designed to be extended by specific authentication implementations (for example, Basic, NTLM, OAuth, or custom token-based methods).

Overview

When Grooper connects to an external content platform over HTTP or HTTPS, it must authenticate with the remote server before performing operations such as browsing, importing, or exporting documents. The HTTP Authentication Method defines the logic for attaching authentication credentials or tokens to outgoing HTTP requests.

Derived classes implement the AuthenticateRequest method, which is called for each HTTP request to apply the appropriate authentication headers or parameters. This enables Grooper to support a wide range of authentication protocols and adapt to the requirements of different external systems.

Usage Notes

• HTTP Authentication Method is not configured directly. Instead, select or configure an authentication method as part of a CMIS Binding or Custom Binding when setting up a CMIS Connection.
• The specific authentication method used depends on the requirements of the target platform (e.g., Basic authentication for simple HTTP servers, NTLM for Windows-integrated authentication, or OAuth for cloud services).
• When configuring a connection, ensure that the selected authentication method matches the server's expectations. Incorrect configuration may result in authentication failures or denied access.
• Custom authentication methods can be implemented by deriving from HTTP Authentication Method and overriding the AuthenticateRequest method to inject custom logic.

Example

To use Basic authentication with a custom binding:

// Pseudocode for configuring a binding with Basic authentication var binding = new MyCustomBinding(); binding.AuthMethod = new BasicAuthenticationMethod("username", "password");

The configured authentication method will be used automatically for all HTTP requests made by the binding.

Derived Types

There are 8 implementations of HTTP Authentication Method.

Anonymous Authentication	Implements HTTP authentication where no credentials or identity are provided to the server.
Auto Authentication	Authenticates HTTP requests using the credentials of the current Windows user.
Basic Authentication	Implements Basic HTTP Authentication for connecting to external content platforms in Grooper.
Exchange OAuth	Implements OAuth 2.0 authentication for connecting Grooper to Microsoft Exchange Online (Office 365) using Azure AD.
NTLM Authentication	Implements NTLM (Windows Integrated) Authentication for connecting to external content platforms in Grooper.
OAuth Service Login	Implements OAuth 2.0 authentication using the client credentials flow for secure server-to-server access in Grooper.
OneDrive OAuth	Implements OAuth 2.0 authentication for connecting Grooper to Microsoft OneDrive and SharePoint Online using a Microsoft account.
SharePoint OAuth	Implements OAuth 2.0 authentication for connecting Grooper to SharePoint Online (365) using Azure AD.

Used By

ExchangeSharePointWeb Service Lookup