[
https://issues.apache.org/jira/browse/YARN-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157781#comment-16157781
]
ASF GitHub Bot commented on YARN-2554:
--------------------------------------
GitHub user thideeeee opened a pull request:
https://github.com/apache/hadoop/pull/271
YARN-2554. RM webproxy uses the client truststore specified in
ssl-client.xml
I want to raise the issue again since the issue affects other application
which runs on YARN. Actually, I see this problem when we run Spark app on Yarn.
Spark launches Spark context web UI with custom SSL certificate when we
enable SSL with "spark.ssl.trustStore" and "spark.ssl.keyStore" properties. In
this case, Yarn web proxy cannot connect the Spark context web UI since the web
proxy cannot verify the SSL cert ("javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed" error is
returned).
We should add an option to set SSL trust store to Yarn RM web proxy. I
added an updated patch, and this patch lets web proxy use an SSL custom
trust-store if it is configured in ssl-client.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/thideeeee/hadoop YARN-2554
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/271.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #271
----
commit 092298dc6883d9c9211af9599cad8fa4cffe517b
Author: Aki Tanaka <[email protected]>
Date: 2017-09-07T21:31:27Z
YARN-2554. RM webproxy uses the client truststore specified in
ssl-client.xml
----
> Slider AM Web UI is inaccessible if HTTPS/SSL is specified as the HTTP policy
> -----------------------------------------------------------------------------
>
> Key: YARN-2554
> URL: https://issues.apache.org/jira/browse/YARN-2554
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Affects Versions: 2.6.0
> Reporter: Jonathan Maron
> Labels: BB2015-05-TBR
> Attachments: YARN-2554.1.patch, YARN-2554.2.patch, YARN-2554.3.patch,
> YARN-2554.3.patch
>
>
> If the HTTP policy to enable HTTPS is specified, the RM and AM are
> initialized with SSL listeners. The RM has a web app proxy servlet that acts
> as a proxy for incoming AM requests. In order to forward the requests to the
> AM the proxy servlet makes use of HttpClient. However, the HttpClient
> utilized is not initialized correctly with the necessary certs to allow for
> successful one way SSL invocations to the other nodes in the cluster (it is
> not configured to access/load the client truststore specified in
> ssl-client.xml). I imagine SSLFactory.createSSLSocketFactory() could be
> utilized to create an instance that can be assigned to the HttpClient.
> The symptoms of this issue are:
> AM: Displays "unknown_certificate" exception
> RM: Displays an exception such as "javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]