[
https://issues.apache.org/jira/browse/RANGER-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15465752#comment-15465752
]
Abhay Kulkarni commented on RANGER-698:
---------------------------------------
[~bosco] A user with name '{USER}' is populated in the ranger database during
ranger-admin initialization. Ranger-admin GUI makes this user available during
policy authoring as one of the items in the drop-down list. Currently, ranger
does not create default policies, as you suggested, out of the box, but these
can be added easily if accessed resources are named generically using accessing
users' names.
CC [~madhan.neethiraj] [~bganesan]
> Ranger policy should support variables like $user
> -------------------------------------------------
>
> Key: RANGER-698
> URL: https://issues.apache.org/jira/browse/RANGER-698
> Project: Ranger
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Don Bosco Durai
> Assignee: Abhay Kulkarni
> Fix For: 0.7.0
>
>
> It would be good to support variables in resources and users.
> E.g.
> HDFS Resource = /home/$user
> or
> Table Resource = ${user}_*
> Users allowed = $user
> Where $user will be expanded to the current user.
> I think, resource substitution will be easy. For permission, we can use key
> word like we use for all users group="public". We can use key word like
> "USER" or something like that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
