[
https://issues.apache.org/jira/browse/IMPALA-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871408#comment-17871408
]
Andrew Sherman commented on IMPALA-11298:
-----------------------------------------
I think this is not a bug. The session user and connection user should match
exactly. I think if we bypass this check more bad things will happen later
> Compare only the short username when checking session user against connection
> user
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-11298
> URL: https://issues.apache.org/jira/browse/IMPALA-11298
> Project: IMPALA
> Issue Type: Bug
> Reporter: Vincent Tran
> Priority: Major
>
> When checking that the session user matches the user authenticated on the
> connection, the usernames compared include the client hostname and the realm
> {code:java}
> if (!connection_username.empty()
> && session_->connected_user != connection_username) {
> return Status::Expected(TErrorCode::UNAUTHORIZED_SESSION_USER,
> connection_username, session_->connected_user);
> }{code}
> This can result in exceptions like so:
> {noformat}
> The user authorized on the connection 'hue/[email protected]' does
> not match the session username 'hue/[email protected]'{noformat}
> We should convert these to short name before comparing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
