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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2018/03/30 01:02:00 UTC

[jira] [Commented] (YARN-8091) Revisit checkUserAccessToQueue RM REST API

    [ https://issues.apache.org/jira/browse/YARN-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420019#comment-16420019 ] 

Wangda Tan commented on YARN-8091:
----------------------------------

1) If login user isn't allowed to access the queue info (who doesn't have admin permission of the queue), 403 will be thrown. 
2) If login user is allowed, we will return an object:

{code}
{"allowed":"true","user":"root1","diagnostics":""}
{code}

> Revisit checkUserAccessToQueue RM REST API
> ------------------------------------------
>
>                 Key: YARN-8091
>                 URL: https://issues.apache.org/jira/browse/YARN-8091
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>            Priority: Critical
>
> As offline suggested by [~sershe]. Currently design of the checkUserAccessToQueue mixed config-related issues (like user doesn't access to the URL) and user-facing output (like requested user is not permitted to access the queue) in the same code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org