[
https://issues.apache.org/jira/browse/HADOOP-10559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986747#comment-13986747
]
Steve Loughran commented on HADOOP-10559:
-----------------------------------------
correction {{addDefaultResource()}} is the way to force in a new conf file on
the classpath -but only before the first security init, and only if the
settings are on the classpath
> add a method to UserGroupInformation to load settings from a given conf file
> ----------------------------------------------------------------------------
>
> Key: HADOOP-10559
> URL: https://issues.apache.org/jira/browse/HADOOP-10559
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.4.0
> Reporter: Steve Loughran
>
> There's no easy way to set up the security parameters of a process unless
> it's set in core-site.xml, because it's just inited via:
> {{initialize(new Configuration(), false);}}
> # If it is defined in an XML resource injected in to the config resource list
> via {{Configuration.addResource()}} -then it *may* get picked up, but only if
> nothing has already created the configs.
> # If it is defined in any other means -you can't get it in.
> This is an issue with client apps that don't have core-site XML files on
> their classpath, and which are loading their configs more dynamically.
> Everything works on an insecure cluster, but try to target a secure one and
> things break.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
