[
https://issues.apache.org/jira/browse/NIFI-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172765#comment-17172765
]
Eduardo Mota Fontes commented on NIFI-3096:
-------------------------------------------
There is a implementation of InvokeHTTP with NTLM support here
[https://github.com/peetkes/nifi-http-processor]
It would be nice to do a merge.
> Issues with NTLM authentication in GetHttp and InvokeHttp processors
> --------------------------------------------------------------------
>
> Key: NIFI-3096
> URL: https://issues.apache.org/jira/browse/NIFI-3096
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Michael Kalika
> Assignee: Karthik Narayanan
> Priority: Major
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
