I have used hive-view for seeing data lineage part in atlas but you know that,we have Atlas and Ranger integration which is mainly talks about "Tag based Policy".I have attached a link which explains demo of "Tag based policy".
In that demo they have used hive view to see/cross check whether security policy is really working or not?
Instead of using "Hive view",can we cross check the same flow/policy with the beeline?.I meant,
can we do something like, login to beeline with hr_user/hr_admin user and check the Atlas-Ranger tag based policy?.
Please tell me is it possible on Atlas-Ranger tech review machine.
Thanks to see you again Ryan,
Did you mean I can login to beeline client console with(hr_user/hr_admin)user credentials and able to see same error(hr_user does not have permission to access ssn and location column) which I was getting in hive veiw right?
1)how to connect beeline using command line option for hr_user/hr_admin.
2)could you please post those commands for connecting to beeline?
Thanks Ryan for your response.
could you please my new question about tag base policy
The demo which is given for Atlas-Ranger tag policy on hortonworks website,i have tried that one.
but now i want that tag base policy should be applicable for my own created tables,database and tags.
please help me.
@Manoj Dhake : To be able to create ur own DB/tables as a user say user1, you will first need an access policy in Ranger for user1 with create permission atleast. I am guessing you know this part.
Then you need to tag your Hive resources through Atlas UI. For that you would need an Atlas Ranger policy which will give appropriate permissions to the user used for tagging .
Once your resources are tagged, you can create a tag based policy in Ranger depending on your need.
Like, if you want user2 to be restricted from seeing any table, say table2 tagged with PII (Table level tag), you create a tag policy with Tag=PII, Under DENY CONDITIONS, put user=user2, and for Component Permissions, select Hive and the Hive operations the user should not be able to perform on the table.
Then add the tag service name in Hive Service by editing Hive service and using field: 'Select Tag Service'.
Now when you try to do any operation on table2 as user2, you will be denied access, even if there is an access policy granting all permissions to user2 on table2.
OR IF you want user2 access to ONLY tagged resources like table2, table3 tagged with 'user' tag, then make sure there is no access based policy for user2 or any of its groups and create a tag based policy with tag='user', in Allow conditions, put user='user2', and for Component Permissions, select Hive and the Hive operations the user should be able to perform on resources tagged with 'user' tag.
Hope this helps. The above 2 examples are typical usages of tag based policies.
Pls vote up if you find the answer useful.