You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2015/10/23 08:16:27 UTC

[jira] [Comment Edited] (TAJO-600) (Umbrella) Tajo Authentication

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

Jihoon Son edited comment on TAJO-600 at 10/23/15 6:15 AM:
-----------------------------------------------------------

I think that we have to make three parts pluggable to support various types of authentication methods. I've attached a file which shows an overall architecture.


was (Author: jihoonson):
I think that we have to make three parts pluggable to support various types of authentication methods.

> (Umbrella) Tajo Authentication
> ------------------------------
>
>                 Key: TAJO-600
>                 URL: https://issues.apache.org/jira/browse/TAJO-600
>             Project: Tajo
>          Issue Type: New Feature
>            Reporter: Min Zhou
>            Assignee: Jihoon Son
>             Fix For: 0.12.0
>
>         Attachments: auth.png
>
>
> Tajo should have the ability to identify its users, otherwise, we can't fair share  the resource between users' queries, we can't do authorization to control the privilege of each user, we can't do auditing.. a lot of things.
> CJ,  who is an expert in this area and who is also the author of Azkaban, would  like to join us to add this feature.
> [~yu.chenjie]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)