[
https://issues.apache.org/jira/browse/ATLAS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885116#comment-16885116
]
ASF subversion and git services commented on ATLAS-3329:
--------------------------------------------------------
Commit 022f2de8954382051a6ed53e4ae91a63f36d4bdd in atlas's branch
refs/heads/branch-2.0 from Nixon Rodrigues
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=022f2de ]
ATLAS-3329 : Update usage of Servlets.getUserName method to
AtlasAuthorizationUtils.getCurrentUserName()
Change-Id: I6bb6649ec9c82690d81f457de051a72eb9812850
(cherry picked from commit 3ad9016cd6f8fba0426262c90e5a97fe795d3843)
> Update usage of Servlets.getUserName method to
> AtlasAuthorizationUtils.getCurrentUserName()
> -------------------------------------------------------------------------------------------
>
> Key: ATLAS-3329
> URL: https://issues.apache.org/jira/browse/ATLAS-3329
> Project: Atlas
> Issue Type: Bug
> Reporter: Nixon Rodrigues
> Assignee: Nixon Rodrigues
> Priority: Major
> Attachments: ATLAS-3329.patch
>
>
> There are instance in code where User name is retrieved from
> httpServletRequest.getRemoteUser() via Servlets.getUserName method.
> If request are coming from proxy then doAs user is impersonate as valid Atlas
> user, getting user name from remote will cause confusion.
> So it make sense to update the usage of Servlets.getUserName to
> AtlasAuthorizationUtils.getCurrentUserName().
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
