[ 
https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757252#action_12757252
 ] 

Namit Jain commented on HIVE-78:
--------------------------------

coping a earlier comment from the jira:

I agree that authentication and authorization (much of what I have been talking 
about in this comment), need to be separated out and while we use the directory 
infrastructure for authentication, we should store the authorization 
information in the metastore as that is specific to our application and no sane 
directory administrator would allow us to touch the directory to support custom 
attributes.

I agree with the above - it might be a good idea to not do password handling in 
hive in the first step - we can add it later if need be. Let us assume that the 
user has already been authenticated by some external entity,
and proceed from there. What do you think ?

> Authentication infrastructure for Hive
> --------------------------------------
>
>                 Key: HIVE-78
>                 URL: https://issues.apache.org/jira/browse/HIVE-78
>             Project: Hadoop Hive
>          Issue Type: New Feature
>          Components: Server Infrastructure
>            Reporter: Ashish Thusoo
>            Assignee: Edward Capriolo
>         Attachments: hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, 
> hive-78.diff
>
>
> Allow hive to integrate with existing user repositories for authentication 
> and authorization infromation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to