GetHTTP processor Error 401:unauthorized

[#1]

I am using a GetHTTP processor to get files from a secured SharePoint site. I created a SSL Context Service using the keystore and truststore jks files from the nifi properties. But when I run this processor I get the error:

ERROR org.apache.nifi.processors.standard.GetHTTP - GetHTTP[id=015b100d-a2b9-1b66-7de9-4b67826a6492] received status code 401:Unauthorized from "the secured sharepoint site"

[#2]

I am trying to connect to a secured sharepoint site using a GetHTTP processor and get the following is the error logs. Please help!!

2017-05-12 13:16:47,790 ERROR [NiFi logging handler] org.apache.nifi.StdErr [NiFi Web Server-7240] INFO org.apache.nifi.web.security.NiFiAuthenticationFilter - Attempting request for (eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJjbj1CTGltYnUsb3U9SW5zdGl0dXRpb24sb3U9UGVvcGxlLGRjPW1kYW5kZXJzb24sZGM9ZWR1IiwiaXNzIjoiTGRhcFByb3ZpZGVyIiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiQkxpbWJ1Iiwia2lkIjozLCJleHAiOjE0OTQ2MTY5OTgsImlhdCI6MTQ5NDYwOTc5OH0.cV2-fJJjiuJNnK8qVQcbJFT0PI_lDU-UfBFxKko-Ddo) GET https://dcdrlhadoop1a:8085/nifi-api/flow/process-groups/015b100c-a2b9-1b66-630f-71e1ddfae949 (source ip: 172.18.58.232)

[#3]

@bhumi limbu

Is this error followed by a stack trace in the nifi-app.log?

[#4]

@Matt Clarke I Matt today when I ran the same process flow somehow I get the same but different error in the log file as follows:

2017-05-15 17:01:27,115 ERROR [NiFi logging handler] org.apache.nifi.StdErr [Timer-Driven Process Thread-7] ERROR org.apache.nifi.processors.standard.GetHTTP - GetHTTP[id=a2b91b66-100d-115b-caa1-ad4dfe1342f1] received status code 401:Unauthorized from https://sharepoint site 2017-05-15 17:01:27,144 ERROR [NiFi logging handler] org.apache.nifi.StdErr [Timer-Driven Process Thread-6] WARN org.apache.http.impl.auth.HttpAuthenticator - NTLM authentication error: Credentials cannot be used for NTLM authentication: org.apache.http.auth.UsernamePasswordCredentials

[#5]

@bhumi limbu

That is a very useful ERROR log message. You appear to be running in to teh following reported issue:

https://issues.apache.org/jira/browse/NIFI-3096

Thanks,

Matt