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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0, 2.5.0
• Component/s: Ranger
• Assignee: Himanshu Maurya
• Reporter: Himanshu Maurya
• Created: 16/Feb/24 05:26
• Updated: 21/Jun/24 15:07
• Resolved: 11/Mar/24 06:17

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.

 

 

Issue Links

• is required by: RANGER-3997 option to use default value when user/group/tag does not have the attribute