Uh oh!
There was an error while loading. Please reload this page.
[SPARK-2750] support https in spark web ui - #1980
Conversation
SparkQA
commented
Sep 5, 2014
Can one of the admins verify this patch? |
andrewor14
commented
Sep 11, 2014
ok to test |
andrewor14
commented
Sep 11, 2014
Looks like this is a duplicate of #1714, which is now closed, however. @WangTaoTheTonic you originally filed the issue to support this. Is there a particular motivation? How is this related to the view ACLs we already have (http://spark.apache.org/docs/latest/security.html)? |
SparkQA
commented
Sep 11, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Sep 11, 2014
QA tests have finished for PR 1980 at commit
|
WangTaoTheTonic
commented
Sep 12, 2014
I did not make very much stuty of SecurityManager, but it only does authentication while not the encryption in communication. |
There was a problem hiding this comment.
It looks like this publicAddress field is never read anymore, so we should remove it.
JoshRosen
commented
Sep 15, 2014
Is Whatever configuration options we end up using, we should add documentation for them to the Spark Security and Configuration guides. |
There was a problem hiding this comment.
This should be spark.worker.ui.port.
There was a problem hiding this comment.
In fact, spark.worker.ui.port is already read on line 51, so this is unnecessary.
JoshRosen
commented
Sep 15, 2014
Also, it looks like this adds configuration options under several (new) namespaces:
Are these the best names? What if we decide to add HTTPS / SSL to other components? What is |
JoshRosen
commented
Sep 15, 2014
What happens if I've configured the web UI to use |
SparkQA
commented
Sep 21, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Sep 21, 2014
QA tests have finished for PR 1980 at commit
|
scwf
commented
Sep 21, 2014
@JoshRosen, here i named the configuration options refer to how hadoop does(actually just use |
SparkQA
commented
Sep 21, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Sep 21, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Sep 21, 2014
QA tests have finished for PR 1980 at commit
|
SparkQA
commented
Sep 21, 2014
QA tests have finished for PR 1980 at commit
|
SparkQA
commented
Sep 21, 2014
QA tests have started for PR 1980 at commit
|
There was a problem hiding this comment.
Might be a good idea to call response.encodeRedirectURL() first.
vanzin
commented
Oct 6, 2014
For some reason I downloaded the patch but it doesn't apply cleanly to my copy of the repo... I'll try again later. |
SparkQA
commented
Oct 7, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Oct 7, 2014
QA tests have finished for PR 1980 at commit
|
There was a problem hiding this comment.
Hi @scwf,
The reason I asked for a comment is that it seems like the method is doing a little more than just that. For example, L238 seems to be doing some sort of parsing of the server string, so it's more than just concatenating the different arguments into a URL.
It would be nice if the comment explained exactly what the relationship between the input and the output is. A unit test wouldn't hurt either.
There was a problem hiding this comment.
Hi @vanzin, actually here i just refer to the code of jetty 9 see(https://github.com/eclipse/jetty.project/blob/master/jetty-util/src/main/java/org/eclipse/jetty/util/URIUtil.java#L726-L733) since there is no newURImethod in spark jetty version(spark use jetty 8).
And L238 is for the case to handle IPv6 address, here we can remove it if unnecessary.
There was a problem hiding this comment.
Could you put that reference in the code itself, so we know where it comes from? Thanks!
SparkQA
commented
Oct 10, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Oct 10, 2014
Tests timed out for PR 1980 at commit |
SparkQA
commented
Oct 10, 2014
QA tests have started for PR 1980 at commit
|
SparkQA
commented
Oct 10, 2014
QA tests have finished for PR 1980 at commit
|
jacek-lewandowski
commented
Oct 22, 2014
@scwf can you take a look at #2739? I created PR which aim is to add SSL support for Akka based connections and for HttpServer which in turn bases on Jetty. I use SSLOptions object to configure SSL. All the settings are being kept in a separate file |
jacek-lewandowski
commented
Oct 22, 2014
Btw. I was trying to do SSL for UI as well. One thing I'm afraid of is that this solution would break any recovery information for Spark Master (different signature of WorkerInfo). Also, it doesn't allow to run the cluster in mixed mode during upgrade - some nodes running older Spark and some nodes running newer Spark, because it changes the signature of messages. Anyway, this is very minor I think. |
scwf
commented
Oct 23, 2014
@jacek-lewandowski, you mean in For the second one "some nodes running older Spark and some nodes running newer Spark", i don't think there is this situation. @JoshRosen@vanzin is this ok to go? I think we can merge this first then in #2739 to unify the ssl configs. |
JoshRosen
commented
Feb 3, 2015
Hi @scwf, I just merged #3571, which added SSL support for Akka and the HTTPServer. That PR added a common configuration mechanism for SSL, plus some useful utilities for testing this functionality. If you're interested, it would be great to revisit HTTPS for the web UI now that we've merged that other patch. |
scwf
commented
Feb 3, 2015
@JoshRosen in that PR now no https support for web ui right? if so i will rework this to support it. |
JoshRosen
commented
Feb 3, 2015
@scwf Yep, that PR only added SSL support to Akka and the HTTP FileServer, not the web UI or the shuffle service. |
scwf
commented
Apr 23, 2015
i am closing this in favor of #5664 |
pritpalm
commented
Dec 15, 2016
I want to enable https on spark UI. I added following config to spark-defaults.config, but when we access spark ui via https::/:8080 or https://:443 or https://:8480, it's not able to connect. spark.ui.https.enabled true |
https://issues.apache.org/jira/browse/SPARK-2750
enable spark web ui to support https, also compatible with old web ui(http).
user can switch between https and http by configure "spark.http.policy".