Vrushali C created YARN-6989:

             Summary: Ensure timeline service v2 codebase gets UGI from 
HttpServletRequest in a consistent way
                 Key: YARN-6989
                 URL: https://issues.apache.org/jira/browse/YARN-6989
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Vrushali C

As noticed during discussions in YARN-6820, the webservices in timeline service 
v2 get the UGI created from the user obtained by invoking getRemoteUser on the 
HttpServletRequest . 

It will be good to use getUserPrincipal instead of invoking getRemoteUser on 
the HttpServletRequest. 

Filing jira to update the code. 

Per Java EE documentations for 6 and 7, the behavior around getRemoteUser and 
getUserPrincipal is listed at:


getRemoteUser, which determines the user name with which the client 
authenticated. The getRemoteUser method returns the name of the remote user 
(the caller) associated by the container with the request. If no user has been 
authenticated, this method returns null.

getUserPrincipal, which determines the principal name of the current user and 
returns a java.security.Principal object. If no user has been authenticated, 
this method returns null. Calling the getName method on the Principal returned 
by getUserPrincipal returns the name of the remote user.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to