Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support SSL connections #3

Open
evren opened this issue Apr 4, 2020 · 3 comments
Open

Support SSL connections #3

evren opened this issue Apr 4, 2020 · 3 comments

Comments

@evren
Copy link
Member

evren commented Apr 4, 2020

Service Controller should provide additional options to provide the trust store parameter.

@PaulJackson123
Copy link
Contributor

I was able to get SSL working, but it required adding the self-signed certificate to the JVM's cacerts.

@evren How do we set the trust store parameter? The javax.net.ssl.trustStore Java system property? Wouldn't that lead to potential conflicts? Or - we figure, let each module keep changing it, but since each nar is loaded in its own class loader, the client will get reinitialized each time? If the assignment of class loaders is at the nar level rather than the processor level then our own processors could conflict with each other.

@PaulJackson123
Copy link
Contributor

ssl_notes.txt

@PaulJackson123
Copy link
Contributor

Nifi has two services - StandardSSLContextService and StandardRestrictedSSLContextService - where one can set properties to identify a trust store for trusted certificates. We could take these properties and see if we can pass them to the http client. Not sure if the Java system property approach will work consistently or if we'll need to pass this to the http client through code. Need to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants