NTLMv2 component
The NTLMv2 component is able to post messages to HTTP(S) endpoints with the Windows NTLM Authentication Protocol. It will post the content it receives from a previous component without altering it.
Configuration
The NTLMv2 component has the following configuration options:
| Property | Description |
|---|---|
URL | URL to the HTTP(s) endpoint that must be reached. It can contain simple expressions like ${header.id} to make it dynamic. |
HTTP Method | Choose between GET, POST, HEAD, PUT, DELETE and PATCH. |
Username | The username used for the NTLMv2 Authentication. |
Password | The password used for the NTLMv2 Authentication. |
Domain | The domain used for the NTLMv2 Authentication. |
Workstation | The workstation used for the NTLMv2 Authentication. |
Use Error Route | Set this to false if the endpoint has a redirect or you don't want HTTP errors to be handled by the error route. |
Remarks
- This component uses the NTLM v2 authentication protocol, NTLM v1 is supported by the default HTTP Component
Custom SSL Certificates
It can be the case that the endpoint you are trying to reach uses an SSL Certificate (HTTPS), this is not a problem for Dovetail as long as it is signed by a default trusted certificate authority.
When the endpoint uses a self-signed certificate, or a certificate not signed by a default trusted certificate authority, the certificate should be retrieved and imported into Dovetail. Unfortunately to date, this has to be done manually by the support staff of Dovetail, please contact your Dovetail provider when necessary.
When you install a flow that uses such an endpoint dovetail will run a pre-install check, to check wether the certificate is valid or not. When using a dynamic url this check can be bypassed and it will show up in the flow logging instead.