I'll take this one back a little. The error with the web server seemed to
have been an out of memory issue. But still curious about the bootstrap
error.
Thanks,
Mike.
On Thu, Mar 9, 2017 at 9:52 PM, Mikhail Sosonkin wrote:
> Hey NiFi team,
>
> I'm getting this error in the bootstrap log:
>
> 20
Hey NiFi team,
I'm getting this error in the bootstrap log:
2017-03-10 05:37:13,330 ERROR [NiFi logging handler] org.apache.nifi.StdErr
[Error] :3355:26: cvc-complex-type.2.4.a: Invalid content was found
starting with element 'transportProtocol'. One of '{inputPort, outputPort}'
is expected.
See
Ok, I think this is fixed. Based on this post[1] I removed all the client
certificates that Safari was showing and it seems to work correctly now.
[1]
https://thedesignspace.net/2014/03/29/website-requires-client-certificate/#.WMH-_RLyuEI
On Thu, Mar 9, 2017 at 8:17 PM, Joe Skora wrote:
> Actu
Actually, it will reach the login page after a few prompts, even without
selection a client cert.
On Thu, Mar 9, 2017 at 8:16 PM, Joe Skora wrote:
> Matt,
>
> I've removed the test user cert I had used previously, as far as I know.
>
> Chrome seems to work ok and doesn't ask for a certificate, b
Matt,
I've removed the test user cert I had used previously, as far as I know.
Chrome seems to work ok and doesn't ask for a certificate, but Safari asks
for a certificate and wants to send the localhost cert since I deleted the
test user cert. Without providing any cert, Safari won't reach the
Without knowing more of your setup, I would guess that your browser is
prompting you based on the available certificates. What happens if you
uninstall the certificate from your browser?
Matt
Sent from my iPhone
> On Mar 9, 2017, at 7:37 PM, Joe Skora wrote:
>
> I have an instance running Ke
I have an instance running Kerberos authentication that still asks for
client certificates.
The authentication seems to work ok, but the certificate issue is quite
annoying. What will fix this?
Thanks,
Joe
I think this is an important concept. We should have something
meaning deprecated but with redirectors to better options. We have
'SeeAlso' for docs so something similar.
On Thu, Mar 9, 2017 at 4:28 PM, Juan Sequeiros wrote:
>
> Hi all,
>
> Lately I've been discussing interacting with messaging
Hi all,
Lately I've been discussing interacting with messaging queues using JMS and
I've had to stop others from trying to use GET and PUT JMS.
I know that ideally if starting from new you should use Consume and Publish
JMS with the JMS controller service connection factory.
Initial impression fr
James, one idea, if your common workflow was wrapped with HandleHttpRequest and
HandleHttpResponse you can reuse them (calling with invokeHttp) since you pass
all the parameters in the request and your workflow use them as attributes.
Your common workflow behaves like a Micro Service.
Of cour
Thank you Joe and Oleg. Reference-able Process Groups sounds like it would
address what we intend to do, without using templates. Which would be fine
and which would presumably serve the same purpose. How far off in the
future is this feature? Six months? A year?
NiFi has a rich and powerful tool
Hello
We have this concept or a very similar concept documented here as a
feature proposal.
https://cwiki.apache.org/confluence/display/NIFI/Reference-able+Process+Groups
It hasn't been worked on yet but will be a really cool thing. The
basic gist is that you can create a process group that acts
I am happy to do this Oleg. Thank you very much for your reply.
Cheers,
Jim
On Thu, Mar 9, 2017 at 6:56 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Jim
>
> I see where you’re going with this and I do believe that it is a valuable
> enterprise feature. Unfortunately, template X
Jim
I see where you’re going with this and I do believe that it is a valuable
enterprise feature. Unfortunately, template XML files are not the bootstrap
source of the flow such as flow.gz file. They are only used for
save/move/migrate/etc., which means any modifications to them are not going t
Good morning. We are developing NiFi workflows with a few key strategic
goals in mind, one of which is this: change common workflows in one place
only, and have those changes ripple through to all process
groups that employ that code.
More specifically: we have a complex but common workflow that w
Thanks for your help.
It works fine after importing client certificate to browser.
On Wed, Mar 8, 2017 at 7:59 PM, Bryan Rosander wrote:
> Hi Kumar,
>
> I would suggest using NiFi's tls-toolkit in order to facilitate
> certificate generation. It can generate a Certificate Authority (to import
16 matches
Mail list logo
