[
https://issues.apache.org/jira/browse/YARN-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870898#comment-13870898
]
Jason Lowe commented on YARN-1600:
----------------------------------
A number of ways to address this, and I'm sure there are others:
* have the RM avoid setting spnego confs on the WebApps setup if the confs have
no values set
* have WebApps avoid setting up username and keytab confs for HttpServer if
those confs have no values set (similar to early patches on YARN-1463)
* if we're worried we need to make sure users are aware that they configured
security but not spnego and want to make that break by default as it does today
then we need a separate config to indicate the user really wants to run with
security but not spnego on the RM web pages
> RM does not startup when security is enabled without spnego configured
> ----------------------------------------------------------------------
>
> Key: YARN-1600
> URL: https://issues.apache.org/jira/browse/YARN-1600
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Jason Lowe
> Priority: Blocker
>
> We have a custom auth filter in front of our various UI pages that handles
> user authentication. However currently the RM assumes that if security is
> enabled then the user must have configured spnego as well for the RM web
> pages which is not true in our case.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
