You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2024/12/06 01:22:00 UTC
[jira] [Resolved] (HDFS-17679) Use saslClient#hasInitialResponse() instead of heuristics in SaslParticipant#createFirstMessage()
[ https://issues.apache.org/jira/browse/HDFS-17679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze resolved HDFS-17679.
-------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
The pull request is now merged. Thanks, [~stoty] !
> Use saslClient#hasInitialResponse() instead of heuristics in SaslParticipant#createFirstMessage()
> -------------------------------------------------------------------------------------------------
>
> Key: HDFS-17679
> URL: https://issues.apache.org/jira/browse/HDFS-17679
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> HDFS currently tries to use a heuristic based on the mechanism name.
> However, SASL has an explcit method to determine if a mechanism requires an inital evaluateChallange() call, which can be universally and unambigiously for this purpose.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org