GitHub user arunmahadevan opened a pull request:

    https://github.com/apache/storm/pull/2169

    [STORM-2563] Remove the workaround to handle missing 
UGI.loginUserFromSubject

    
    
https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/security/auth/kerberos/AutoTGT.java#L225
    
    The "userCons.setAccessible(true)" invokes constructor of a package private 
class bypassing the Java access control checks and raising red flags in our 
internal security scans.
    
    The "loginUserFromSubject(Subject subject)" has been added to UGI 
(https://issues.apache.org/jira/browse/HADOOP-10164) and available since Hadoop 
version 2.3 released over three years ago 
(http://hadoop.apache.org/releases.html).
    
    I think the workaround is no longer required since the case will not happen 
when using hadoop-common versions >= 2.3
    
    @revans2 , could you take a look ?

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

    $ git pull https://github.com/arunmahadevan/storm STORM-2563

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

    https://github.com/apache/storm/pull/2169.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 #2169
    
----
commit 2fac9787c711ee30145c4275547629394df1c67b
Author: Arun Mahadevan <[email protected]>
Date:   2017-06-21T04:41:36Z

    [STORM-2563] Remove the workaround to handle missing 
UGI.loginUserFromSubject
    
    
https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/security/auth/kerberos/AutoTGT.java#L225
    
    The "userCons.setAccessible(true)" invokes constructor of a package private 
class bypassing the Java access control checks
    and raising red flags in our internal security scans.
    
    The "loginUserFromSubject(Subject subject)" has been added to UGI 
(https://issues.apache.org/jira/browse/HADOOP-10164)
    and available since Hadoop version 2.3 released over three years ago 
(http://hadoop.apache.org/releases.html).
    
    I think the workaround is no longer required since the case will not happen 
when using hadoop-common versions >= 2.3

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to