[jira] [Created] (ZEPPELIN-4325) Upgrade livy to 0.6
Jeff Zhang created ZEPPELIN-4325: Summary: Upgrade livy to 0.6 Key: ZEPPELIN-4325 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4325 Project: Zeppelin Issue Type: Improvement Affects Versions: 0.9.0 Reporter: Jeff Zhang -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [zeppelin] zjffdu commented on issue #3441: [ZEPPELIN-4324]: Support two-way SSL authentication.
zjffdu commented on issue #3441: [ZEPPELIN-4324]: Support two-way SSL authentication. URL: https://github.com/apache/zeppelin/pull/3441#issuecomment-529303622 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. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [zeppelin] fdeantoni opened a new pull request #3441: [ZEPPELIN-4324]: Support two-way SSL authentication.
fdeantoni opened a new pull request #3441: [ZEPPELIN-4324]: Support two-way SSL authentication. URL: https://github.com/apache/zeppelin/pull/3441 ### 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: - 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. ### 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: - zeppelin.livy.ssl.keyStore: Path to keystore containing client certificate and key - zeppelin.livy.ssl.keyStorePassword: Password of keystore - zeppelin.livy.ssl.keyStoreType: Either JKS or PKCS12 - zeppelin.livy.ssl.trustStore: Path to trust store containing proxy host certificate - zeppelin.livy.ssl.trustStorePassword: Password of trust store - zeppelin.livy.ssl.keyStoreType: Either JKS or PKCS12 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (ZEPPELIN-4324) Livy Interpreter support two way SSL
Ferdinand de Antoni created ZEPPELIN-4324:
-
Summary: Livy Interpreter support two way SSL
Key: ZEPPELIN-4324
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4324
Project: Zeppelin
Issue Type: Improvement
Components: livy-interpreter
Reporter: Ferdinand de Antoni
Our Livy instance is behind a reverse proxy that protects Livy with two way SSL
(also known as client side SSL or mutual SSL authentication). To support this,
the http client in the Livy interpreter should be extended to also receive "key
material" e.g.:
{code:java}
SSLContext sslContext = SSLContexts.custom()
.loadKeyMaterial(keyStore, password)
.loadTrustMaterial(trustStore)
.build(); {code}
Naturally, adding the keyStore should only be done if a relevant keystore
property (to be added with this Jira as well) is not blank.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [zeppelin] asfgit closed pull request #3336: [ZEPPELIN-4091] Fix concurrent autocomplete and execute for Ipython
asfgit closed pull request #3336: [ZEPPELIN-4091] Fix concurrent autocomplete and execute for Ipython URL: https://github.com/apache/zeppelin/pull/3336 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
