You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/03/24 14:42:00 UTC
[jira] [Updated] (YARN-11953) Fix authentication type checking in Capacity Scheduler UI
[ https://issues.apache.org/jira/browse/YARN-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated YARN-11953:
----------------------------------
Labels: pull-request-available (was: )
> Fix authentication type checking in Capacity Scheduler UI
> ---------------------------------------------------------
>
> Key: YARN-11953
> URL: https://issues.apache.org/jira/browse/YARN-11953
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Benjamin Teke
> Priority: Major
> Labels: pull-request-available
>
> Capacity Scheduler UI currently [checks |https://github.com/apache/hadoop/blob/1995d34a54be4e8cc928b58cd0d57d3698462ebd/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-capacity-scheduler-ui/src/main/webapp/src/lib/api/YarnApiClient.ts#L245]the {{hadoop.security.authentication}} config for ensuring what the http authentication type is (to see if the user.name param needs to be added for requests). This is incorrect, {{hadoop.http.authentication.type}} controls the actual webUI authentication type. This causes an issue where if the global auth type is kerberos, but the webUIs use simple, YARN will reject every query made by the Capacity Scheduler UI. To fix this the auth checks should use {{hadoop.http.authentication.type.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org