Hi Aldrin,
This was with the original package. Also, I’ve attached the verbose output.
Thanks,
Dan
From: Aldrin Piri [mailto:aldrinp...@gmail.com]
Sent: Tuesday, February 07, 2017 5:18 PM
To: users@nifi.apache.org
Subject: Re: GetTwitter - Security/Certificate Issue
Hi Dan
Any thoughts?
-Dan
From: Aldrin Piri [mailto:aldrinp...@gmail.com<mailto:aldrinp...@gmail.com>]
Sent: Wednesday, February 01, 2017 5:05 PM
To: users@nifi.apache.org<mailto:users@nifi.apache.org>
Subject: Re: GetTwitter - Security/Certificate Issue
Hi Dan,
I did a bit of poking
t;
>
> -Dan
>
>
>
> *From:* Aldrin Piri [mailto:aldrinp...@gmail.com]
> *Sent:* Wednesday, February 01, 2017 5:05 PM
>
> *To:* users@nifi.apache.org
> *Subject:* Re: GetTwitter - Security/Certificate Issue
>
>
>
> Hi Dan,
>
>
>
> I did a bit of
you need any additional
> info to help diagnose the issue!
>
>
>
> Thanks,
>
>
>
> Dan
>
>
>
>
>
> *From:* Aldrin Piri [mailto:aldrinp...@gmail.com]
> *Sent:* Tuesday, January 31, 2017 2:20 PM
> *To:* users@nifi.apache.org
> *Subject:* Re:
To: users@nifi.apache.org
Subject: Re: GetTwitter - Security/Certificate Issue
Hi Dan,
The GetTwitter processor does not make use of an Apache NiFi SSLContextService
so the certificate chain issues are likely more tied to the JVM/OS
specifically. Did a quick check on some of the instances I am
Hi Dan,
The GetTwitter processor does not make use of an Apache NiFi
SSLContextService so the certificate chain issues are likely more tied to
the JVM/OS specifically. Did a quick check on some of the instances I am
running and Twitter seems to be operating normally.
Could you share some more
Hi Dan,
Yes, currently your processor is saying that it receives a certificate
identifying https://www.twitter.com (or whatever the actual URL is) but it
cannot build a complete chain between the presented certificate and a known
CA/trusted certificate. This is because by default, NiFi doesn’t
