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

Policy condition expressions are split by the Ranger UI on commas

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0
    • Ranger
    • None

    Description

      While using attributes with default values introduced in RANGER-3997 like GET_USER_ATTR('state', 'null') in policy condition.
      It is observed that ranger is splitting condition string in to 2 parts separated by comma of the parameters passed to GET_USER_ATTR(), due to this it is not taking default value and conditions are converted to invalid strings.
      Kindly refer to screenshots attached below.

       

       

      Attachments

        1. image-2024-02-20-17-28-17-767.png
          44 kB
          Himanshu Maurya
        2. image-2024-02-20-17-28-28-558.png
          44 kB
          Himanshu Maurya
        3. image-2024-02-20-17-39-05-432.png
          192 kB
          Himanshu Maurya
        4. Screenshot 2024-02-15 at 5.07.02 PM.png
          127 kB
          Himanshu Maurya
        5. Screenshot 2024-02-15 at 5.20.36 PM.png
          43 kB
          Himanshu Maurya
        6. Screenshot 2024-02-15 at 5.27.54 PM.png
          182 kB
          Himanshu Maurya
        7. Screenshot 2024-02-20 at 5.26.46 PM.png
          128 kB
          Himanshu Maurya

        Issue Links

          Activity

            People

              hmaurya Himanshu Maurya
              hmaurya Himanshu Maurya
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: