CODEWITHSUNDEEP
getapache-nifi
papelr
papelr

Reputation: 438

NiFi: Configuring SSLContextService for GetHTTP or InvokeHTTP

I am trying to use WMATA's (the DC system) Metro API, and use NiFi to pull in some live Train Position data. I currently have tried to use both GetHTTP and InvokeHTTP, but no luck. My confusion comes from two areas:

1) How to configure the processor itself?

2) Configuring the SSLContextService?

The Metro website gives a Primary and Secondary key - but I'm not sure how to parse that information, when the SSLContextDriver config asks for KeyStore filename, etc.

My GetHTTP config:

enter image description here

And my SSL config:

enter image description here

I get errors when I run the GetHTTP processor: enter image description here

I hope my issue makes sense. Thanks

Upvotes: 0

Views: 2048

Answers (1)

Bryan Bende
Bryan Bende

Reputation: 18670

For the specific error message you have show, the URL you specified has contentType={contentType} which is invalid. If you wanted to reference a flow file attribute, or variable, it would need to be ${contentType}. Otherwise if you really want to literally pass {contentType} then I think you would need to URL encode the brackets first.

For your SSL Context service, I believe in this case you want to set the truststore to CA certs instead of the keystore. It is similar to how your browser has truststores and verifies server identities when you go to an https page. You would only specify the keystore if you needed the GetHttp/InvokeHttp processor to also provide an identity so the other server could verify the identity of the processor.

Upvotes: 1

Related Questions