[ 
https://issues.apache.org/jira/browse/YARN-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979538#comment-15979538
 ] 

ASF GitHub Bot commented on YARN-6457:
--------------------------------------

GitHub user sanjaypujare opened a pull request:

    https://github.com/apache/hadoop/pull/216

    YARN-6457  use existing conf object as sslConf object in WebApps for the 
builder to use for the HttpServer2

    Merged from 2.7.1 branch

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sanjaypujare/hadoop YARN-6457.trunk.sanjay

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/216.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 #216
    
----
commit 8218dab40b96984a383aa4ad9fa6ae2b053cff4a
Author: Sanjay Pujare <[email protected]>
Date:   2017-04-21T23:00:13Z

    YARN-6457  use existing conf object as sslConf object in WebApps for the 
builder to use for the HttpServer2

----


> Allow custom SSL configuration to be supplied in WebApps
> --------------------------------------------------------
>
>                 Key: YARN-6457
>                 URL: https://issues.apache.org/jira/browse/YARN-6457
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: webapp, yarn
>            Reporter: Sanjay M Pujare
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Currently a custom SSL store cannot be passed on to WebApps which forces the 
> embedded web-server to use the default keystore set up in ssl-server.xml for 
> the whole Hadoop cluster. There are cases where the Hadoop app needs to use 
> its own/custom keystore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to