You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Himanshu Maurya (Jira)" <ji...@apache.org> on 2024/02/16 05:29:00 UTC

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

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

Himanshu Maurya updated RANGER-4719:
------------------------------------
    Summary:  Policy condition expressions are split by the Ranger UI on commas  (was:  Condition expressions are split by the Ranger UI on commas)

>  Policy condition expressions are split by the Ranger UI on commas
> ------------------------------------------------------------------
>
>                 Key: RANGER-4719
>                 URL: https://issues.apache.org/jira/browse/RANGER-4719
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Himanshu Maurya
>            Assignee: Himanshu Maurya
>            Priority: Major
>         Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png
>
>
> While using 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.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)