[NIFI-3096] Issues with NTLM authentication in GetHttp and InvokeHttp processors

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: Extensions
• Assignee: Unassigned
• Reporter: Michael Kalika
• Created: 23/Nov/16 20:10
• Updated: 10/Nov/22 16:06
• Resolved: 10/Nov/22 16:03

Description

GetHttp and InvokeHttp do not support HTTP endpoints protected with NTLM authentication. This functionality is needed for working with services and APIs hosted in Windows systems.

Here's a log with error:
2016-11-23 17:45:22,272 WARN [Timer-Driven Process Thread-7]
o.a.http.impl.auth.HttpAuthenticator NEGOTIATE authentication error: No valid
credentials provided (Mechanism level: No valid credentials provided (Mechanism
level: Failed to find any Kerberos tgt))
2016-11-23 17:45:22,272 WARN [Timer-Driven Process Thread-7]
o.a.http.impl.auth.HttpAuthenticator NTLM authentication error: Credentials
cannot be used for NTLM authentication:
org.apache.http.auth.UsernamePasswordCredentials
2016-11-23 17:45:22,274 ERROR [Timer-Driven Process
Thread-7] o.a.nifi.processors.standard.GetHTTP
GetHTTP[id=91ce7dfd-0158-1000-1c53-cf24cf132983] received status code
401:Unauthorized from http://internal.api.ep/dosomething

and a discussion about this issue
https://community.hortonworks.com/questions/68097/issues-with-gethttp-and-ntlm-authentication-in-nif.html

Issue Links

• is related to: NIFI-6250 Add Kerberos authentication support to InvokeHTTP Processor
• relates to: NIFI-8905 Add NTLM authentication support to the gitflowpersistenceprovider