[ZEPPELIN-4324]: Support two-way SSL authentication. #3441
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Livy can run behind a reverse proxy that requires SSL authentication. To support this, three additional properties have been added: - zeppelin.livy.ssl.keyStore - zeppelin.livy.ssl.keyStorePassword - zeppelin.livy.ssl.keyStoreType The keystore type can either be JKS or PKCS12. The default is JKS. To keep things streamlined, a property `zeppelin.livy.ssl.trustStoreType` has been been added as well. Default value is also JKS.
|
Thanks for the contribution @fdeantoni Does it keep backward compatibility ? I mean does it work in the non-proxy mode with the old configuration. And have you configured your travis ? I don't see the travis build link here. |
|
The changes should be backwards compatible. The keyStore is only added if the property I just set up travis and triggered a build: https://travis-ci.org/fdeantoni/zeppelin |
|
Thanks, PR LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
Livy can run behind a reverse proxy that requires SSL authentication.
To support this, three additional properties have been added:
The keystore type can either be JKS or PKCS12. The default is JKS. To
keep things streamlined, a property
zeppelin.livy.ssl.trustStoreTypehas been been added as well. Default value is also JKS.
What type of PR is it?
Improvement
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4324
How should this be tested?
Set up a livy instance behind a reverse proxy (e.g. HAProxy) that requires two way SSL authentication to access it. Configure the Livy interpreter to access this instance by setting the following properties: