ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Velmurugan Periasamy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-2180) Handle token replacement correctly when token is not defined in the request context
Date Wed, 22 Aug 2018 17:35:00 GMT

     [ https://issues.apache.org/jira/browse/RANGER-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Velmurugan Periasamy updated RANGER-2180:
-----------------------------------------
    Fix Version/s: 2.0.0

> Handle token replacement correctly when token is not defined in the request context
> -----------------------------------------------------------------------------------
>
>                 Key: RANGER-2180
>                 URL: https://issues.apache.org/jira/browse/RANGER-2180
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: master, 2.0.0
>
>
> When a policy resource contains a token (such as \{USER}), and request context does not
have an entry for the token (in this case, USER), then the replacement fails and the expanded
policy resource is set to null. A null policy-resource will not match any policy, and may
cause NPE.
> In such case, the original policy resource string should be returned as the expanded
policy resource string.



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

Mime
View raw message