You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/02/08 14:51:00 UTC

[jira] [Updated] (HBASE-28337) Positive connection test in TestShadeSaslAuthenticationProvider runs with Kerberos instead of Shade authentication

     [ https://issues.apache.org/jira/browse/HBASE-28337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HBASE-28337:
-----------------------------------
    Labels: pull-request-available  (was: )

> Positive connection test in TestShadeSaslAuthenticationProvider runs with Kerberos instead of Shade authentication
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-28337
>                 URL: https://issues.apache.org/jira/browse/HBASE-28337
>             Project: HBase
>          Issue Type: Test
>    Affects Versions: 2.6.0, 2.4.17, 3.0.0-beta-1, 2.5.7, 2.7.0
>            Reporter: Andor Molnar
>            Assignee: Andor Molnar
>            Priority: Major
>              Labels: pull-request-available
>
> The positive test (testPositiveAuthentication) in TestShadeSaslAuthenticationProvider doesn't create a new user in user1.doAs(), so it will use the already Kerberos authenticated user instead of re-authenticating with the token. 
> As a consequence it doesn't reveal a problem introduced with HBASE-23881 which will cause clients to timeout if authenticated with a SASL mech which doesn't create a reply token in case of successful authentication.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)