Uploaded image for project: 'Ranger'
  1. Ranger
  2. RANGER-2180

Handle token replacement correctly when token is not defined in the request context

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • master
    • 2.0.0, 1.2.0
    • Ranger
    • None

    Description

      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.

      Attachments

        Activity

          People

            abhayk Abhay Kulkarni
            abhayk Abhay Kulkarni
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: