In this article
Overview
You can use this account type to connect the HTTP Client Snap with data sources that use the NTLM account.
Prerequisites
None.
Limitations and Known Issues
None.
Account Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (
): Indicates a list that is dynamically populated based on the configuration.Expression icon (
): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.Add icon (
): Indicates that you can add fields in the field set.Remove icon (
): Indicates that you can remove fields from the field set.
Field Name | Field Type | Description |
|---|---|---|
Label* Default Value: N/A | String | Specify a unique name for the account. |
Username* Default Value: N/A | String/Expression | Specify the username that you want to use to log into NTLM. |
Password* Default Value: N/A | String/Expression | Specify the password associated with the username listed in the field above. |
Domain* Default Value: N/A | String/Expression | Specify the name of the NETBIOS domain in which the account is configured. |
Release Snap Pack Version Date Type Updates February 2025 440patches29956 Latest Fixed an issue with the HTTP Client Snap where reserved characters in the MIME type caused the Snap to fail. Enhanced the GraphQL Client Snap to support pagination interval that enables you to use the APIs with rate limits. February 2025 main29887 Stable Added the gRPC Client Snap that enables you to interact with a gRPC (Google Remote Procedure Call) server to invoke its services. Learn more. November 2024 439patches29124 Latest Fixed an issue in the GraphQL Client Snap where improper extensions caused a validation error; however, it resulted in an empty error view when the Route Error Data to Error View was enabled. Fixed an issue with the GraphQL Client Snap that did not load the November 2024 main29029 Stable Updated and certified against the current SnapLogic Platform release. August 2024 438patches28567 Latest Fixed a token refresh issue with the GraphQL Client Snap (configured with the OAuth2 Account) wherein the access token expired before the periodic platform refresh, and the Snap displayed 401 and 403 errors. Now, the account refreshes the access token and retries query execution, ensuring seamless integration. August 2024 438patches28365 Latest The GraphQL Client Snap now includes an improved error-handling mechanism that emulates how the errors are reported in the raw GraphQL response. This enhancement provides additional context and pagination to the error output, which was previously limited to one page. Learn more. Enhanced the GraphQL Client Snap with the Include extensions checkbox to support extensions that enable you to access query content and extension data in a structure, similar to the GraphQL response. The non-standard fields in the GraphQL response are now ignored to avoid a possible error. August 2024 438patches28040 Latest Enhanced the HTTP Client Snap with improved handling of redirect URL encoding to minimize runtime errors. August 2024 main27765 Stable Updated and certified against the current SnapLogic Platform release. May 2024 437patches27592 Latest Updated the API Suite Snaps to process authentication information from incoming documents to support features such as Secrets manager-based credentials. May 2024 437patches27587 Latest Fixed an issue with the HTTP Client Snap that caused May 2024 437patches26862 Latest Fixed an issue with the HTTP Client Snap where redirect URLs containing spaces were not properly encoded, resulting in runtime errors. May 2024 437patches26826 Latest Enhanced the SSL OAuth2 Account with the Send Client Data as Basic Auth header checkbox that enables you to send the client information as a header to the OAuth endpoint. May 2024 437patches26522 Latest Enhanced the OAuth2 account with Snaplex support for executing OAuth2 operations. May 2024 437patches26491 Latest Fixed an issue with the GraphQL Client Snap that displayed an error when passing the May 2024 main26341 Stable Updated and certified against the current SnapLogic Platform release. February 2024 436patches25508 Latest Enhanced the HTTP Client Snap to optimize the memory usage by accumulating the February 2024 463patches25211 Latest Enhanced the GraphQL Client Snap to include detailed stack trace, error message, and reason within the Snap error view output. February 2024 main25112 Stable Updated and certified against the current SnapLogic Platform release. November 2023 435patches25047 Latest Fixed an issue that caused the HTTP Client Snap to fail when the Basic Authentication account password contained special characters. November 2023 435patches24708 Latest Added support for the SSL OAuth2 Account. The HTTP Client and GraphQL Client Snaps now support accessing usernames and passwords from the Basic Authentication account. The HTTP Client Snap also has this capability for the Digest Authentication, NTLM, SSL, and Google Service accounts. Enhanced the API Suite OAuth2 Account with the Send client data as Basic Auth header checkbox to pass the client data as a part of the Basic Authentication header when generating a token. November 2023 435patches24208 Latest Fixed an issue with the HTTP Client Snap that caused incorrect parsing of the November 2023 435patches23943 Latest Fixed an issue with the GraphQL Client Snap that displayed a null pointer exception when the Header authenticated checkbox in the OAuth2 Account is deselected. The Snap now passes the credentials appropriately using URL parameters when the Header authenticated field is deselected. November 2023 main23721 Stable Added the Google Service Account to the HTTP Client Snap, which enables you to connect to various Google Cloud endpoints such as Analytics 4 and Compute Engine. August 2023 434patches23079 Latest Fixed an issue with the SnapLogic SSL Account for the HTTP Client Snap where a blank keystore or truststore URL caused an error during account configuration. August 2023 434patches22631 Latest Fixed an issue with the HTTP Client Snap that displayed incorrect cookie information, with a null value in the cookies when you have duplicate cookies in the header. The Snap now displays the cookie information correctly. August 2023 main22460 Stable Updated and certified against the current SnapLogic Platform release. May 2023 433patches22065 Latest Fixed an issue with the GraphQL Client Snap that caused an error even when the variable value was defined in the previous Snap. May 2023 433patches21959 Latest Fixed an issue with the HTTP Client Snap that caused an intermittent connectivity issue, which resulted in a May 2023 433patches21860 Latest Fixed an issue with the HTTP Client Snap where the Snap now conceals the additional authentication headers in the debug information for Secured Headers Account. May 2023 433patches21346 Latest Fixed an issue with the HTTP Client Snap where the validation of the SSL Account for a specified Keystore or Truststore value failed despite providing the correct password. May 2023 433patches21307 Latest Fixed an issue with the HTTP Client Snap that caused pagination to fail when the next Snap in the pipeline could modify the input document (for example, the Mapper Snap). Behavior Change: May 2023 433patches21140 Latest Fixed an issue affecting the HTTP Client Snap, which caused it to hang for an extended period when the user-agent contained the term The HTTP Client Snap is enhanced with the Prevent URL encoding checkbox. This checkbox enables you to control whether the Snap should automatically encode the URL or prevent the URL encoding based on your preference. May 2023 main21015 Stable Introduced the GraphQL Client Snap, which enables you to query a GraphQL endpoint and retrieve data. This Snap features a built-in query builder to help you efficiently build queries. February 2023 432patches20818 Latest Fixed an issue with the HTTP Client Snap that caused encoding of spaces in the query portion of an URL with a plus sign (+) instead of percent-encoding (%). This fix changes the default behavior to percent-encoding through the Use form encoding for spaces checkbox, which is deselected by default. Select this checkbox to enable the Snap to encode any space characters in query parameters using the plus sign (+). Updated the HTTP Client Snap to stop sending unnecessary headers in GET requests that do not have an entity defined. February 2023 432patches20054 Latest For Snaps using AWS Signature V4 accounts, DNS canonical names are now supported for S3 buckets. February 2023 main19844 Stable Upgraded with the latest SnapLogic Platform release. November 2022 431patches19006 Latest The HTTP Client Snap does not fail when making a PATCH request containing an empty response body and location in the Headers. The Snap checks the entity length if the response entity is empty and skips the data conversion. November 2022 main18944 Stable The HTTP Client Snap now accepts the default value October 2022 430patches18454 Latest and Stable Introduced the API Suite Snap Pack that contains the HTTP Client Snap. This Snap unifies all supported HTTP methods: GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, and PATCH that you can execute on a REST API service endpoint. February 2025 February 2025Query Builder properly.
By default, the Snap executes the standard redirect behavior. However, if a redirect URL contains unencoded spaces, or special characters, or any other improper format that could potentially cause issues, the Snap encodes the URL before redirecting, ensuring a successful runtime execution.NullPointerException when the Retry-After header contained a decimal value in the 429 (Too Many Requests) response.Float data type query variables to the endpoint.Request History objects only when you select the Enable debug checkbox. Now, the Snap displays debug information and lint warnings only (in both Error view and Output view) when you select the Enable debug checkbox.boundary parameter by some REST endpoints. If you need to specify a character set, enter it in the individual parts of the request, as the charset parameter has been removed from the multipart content-type.404 error .
With the 433patches21307, pagination evaluation occurs before sending the output to the output view. Therefore, if snap.out.totalCount is part of the Has next or any other pagination properties, the Snap will not include the count in the output corresponding to the request that produced the output document.java.*/* for the Accept header, which communicates to the server that the Snap can handle all forms of response content types.