NTLM Authentication

Implements NTLM (Windows Integrated) Authentication for connecting to external content platforms in Grooper.

Remarks

NTLM Authentication enables Grooper to authenticate HTTP requests using Windows credentials, following the MS-NLMP protocol. NTLM is commonly used in enterprise environments for authenticating against Microsoft servers, file shares, and other Windows-based services.

Overview

When NTLM Authentication is selected as the authentication method for a CMIS Binding or Custom Binding, Grooper will use the specified user name, password, and domain to authenticate with the target server. This method supports single sign-on scenarios and is compatible with Active Directory environments.

NTLM provides a challenge-response mechanism for authentication, offering more security than basic authentication, but is still best used over secure (HTTPS) connections to protect credentials.

Usage Notes

• Configure the 'User Name', 'Password', and 'Domain' properties with the credentials required by the target server or Active Directory environment.
• Use NTLM Authentication when connecting to Windows servers, SharePoint, or other services that require Windows Integrated Authentication.
• Ensure the user account has the necessary permissions and that the domain is specified correctly for domain accounts.
• For local accounts, the 'Domain' property may be left blank or set to the local machine name.

Example

// Pseudocode for configuring a binding with NTLM authentication var binding = new MyCustomBinding(); binding.AuthMethod = new NtlmAuthentication { UserName = "jdoe", Password = "mypassword", Domain = "MYDOMAIN" };

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

For more information on authentication options and security best practices, see the Grooper documentation on CMIS+ connections and authentication methods.

Properties

Name	Type		Description
User Name	String	►	The user name to be used for authentication. The 'User Name' property specifies the Windows account name that Grooper will use when authenticating with the target server using NTLM Authentication. Enter the user name as required by your environment. This may be a simple name (e.g., jdoe), or a domain-qualified name (e.g., DOMAIN\user), depending on the server's requirements. Ensure that the user account has the necessary permissions to access the desired resources. Incorrect or missing user names will result in authentication failures.
Password	String	►	The password that will be used for access. The 'Password' property specifies the secret credential associated with the 'User Name' for NTLM Authentication. This value is securely stored in an encrypted form within Grooper, but is transmitted to the server as part of the authentication process when making requests. For security, always use strong, unique passwords and ensure that connections are made over HTTPS to prevent interception of credentials. If the password is changed on the server, be sure to update this property in Grooper to maintain connectivity.
Domain	String	►	The Windows Active Directory domain name that will be used for authentication. The 'Domain' property specifies the Windows domain to use for authentication. For domain accounts, enter the domain name exactly as required by your Active Directory environment (e.g., MYDOMAIN). For local accounts, you may leave this property blank or specify the local machine name. The correct domain is essential for successful authentication in enterprise environments. If you are unsure of the domain, consult your system administrator or IT department.

Used By

ExchangeSharePointWeb Service Lookup