ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Created] (RANGER-2180) Handle token replacement correctly when token is not defined in the request context
Date Wed, 01 Aug 2018 20:07:00 GMT
Abhay Kulkarni created RANGER-2180:
--------------------------------------

             Summary: 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
             Fix For: master


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