[jira] [Commented] (RANGER-3997) option to use default value when user/group/tag does not have the attribute
[
https://issues.apache.org/jira/browse/RANGER-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817846#comment-17817846
]
Himanshu Maurya commented on RANGER-3997:
-
Hi [~madhan], Thank you for your confirmation
I have created the issue :- RANGER-4719
I will feel happy to contribute on this
Thanks and Regards
> option to use default value when user/group/tag does not have the attribute
> ---
>
> Key: RANGER-3997
> URL: https://issues.apache.org/jira/browse/RANGER-3997
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3997.patch, 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
>
>
> Consider following row-filter expression that refers to a user attribute:
> {code:java}
> dept = ${{USER.dept}}{code}
>
> For this expression to evaluate correctly, all users who run query on the
> table should have an attribute named dept. To handle users for whom this
> attribute is not defined, an additional policy-item would be required, as
> shown below:
> {noformat}
> 1. "condition": "!HAS_USER_ATTR('dept')", "filterExpr": "dept = -1"
>
> 2. "filterExpr": "dept = ${{USER.dept}}"{noformat}
>
> Ability to use a default value when the attribute doesn't exist will
> eliminate the need for the additional policy item, like:
> {noformat}
> "filterExpr": "dept = ${{GET_USER_ATTR('dept', -1)}}{noformat}
>
> Added following macros to support optional default value:
>
> ||Macro||With default value||Description||Example return value||
> |GET_TAG_NAMES()|GET_TAG_NAMES('none')|Names of tags associated with the
> resource, separated by a comma|PII,PCI|
> |GET_TAG_ATTR_NAMES()|GET_TAG_ATTR_NAMES('none')|Names of attributes in tags
> associated
> with the resource, separated by a comma|piiType,score|
> |GET_TAG_ATTR('score')|GET_TAG_ATTR('score', 0)|Attribute value in tags
> associated with the
> resource, separated by a comma|0|
> |GET_UG_NAMES()|GET_UG_NAMES('none')|Names of groups the user belongs to,
> separated by a comma|analyst,manager|
> |GET_UG_ATTR_NAMES()|GET_UG_ATTR_NAMES('none')|Names of all attributes in
> groups the user
> belongs to, separated by a comma|dept,site|
> |GET_UG_ATTR('site')|GET_UG_ATTR('site', 'none')|Attribute value in groups
> the user belongs
> to, separated by a comma|10,20|
> |GET_UR_NAMES()|GET_UR_NAMES('none')|Names of roles assigned to the user,
> separated by a comma|data-steward,admin|
> |GET_USER_ATTR_NAMES()|GET_USER_ATTR_NAMES('none')|Names of all attributes of
> the user,
> separated by a comma|name,email|
> |GET_USER_ATTR('email')|GET_USER_ATTR('email', 'none')|Value of user
> attribute|n...@domain.com|
>
> For each macro listed above, there is another version with *_Q* added to the
> name, like:
> {code:java}
> GET_TAG_NAMES_Q(){code}
> These macros would quote each value, like:
> {code:java}
> 'PII','PCI'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4719) 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:
Attachment: Screenshot 2024-02-15 at 5.27.54 PM.png
> 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=639,height=372!
>
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
>
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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)
[jira] [Updated] (RANGER-4719) 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:
Description:
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!
was:
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=639,height=372!
!Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
!Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
> 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)
[jira] [Updated] (RANGER-4719) 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:
Attachment: Screenshot 2024-02-15 at 5.20.36 PM.png
> 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
>
>
> 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=639,height=372!
>
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
>
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4719) 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:
Attachment: Screenshot 2024-02-15 at 5.07.02 PM.png
> 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
>
>
> 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=639,height=372!
>
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
>
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4719) Condition expressions are split by the Ranger UI on commas
Himanshu Maurya created RANGER-4719:
---
Summary: 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
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=639,height=372!
!Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
!Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4699) Update the execution of setServiceDef call in App.jsx
[ https://issues.apache.org/jira/browse/RANGER-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-4699: --- Attachment: 0001-RANGER-4699.patch > Update the execution of setServiceDef call in App.jsx > - > > Key: RANGER-4699 > URL: https://issues.apache.org/jira/browse/RANGER-4699 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger >Reporter: Mugdha Varadkar >Assignee: Dhaval Rajpara >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4699.patch > > > Need minor code update in executing the setServiceDef() call in App.jsx -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3997) option to use default value when user/group/tag does not have the attribute
[
https://issues.apache.org/jira/browse/RANGER-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817718#comment-17817718
]
Madhan Neethiraj commented on RANGER-3997:
--
[~hmaurya] - it is likely that the entered expression is split by the UI on
commas. [~Dhaval.Rajpara], [~brijesh.bhalala], [~ni3galave] - can you please
help? BTW, this issue is not seen with the latest React UI in the master
branch; it is only seen with earlier version of UI implemented in Backbone.
> option to use default value when user/group/tag does not have the attribute
> ---
>
> Key: RANGER-3997
> URL: https://issues.apache.org/jira/browse/RANGER-3997
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3997.patch, 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
>
>
> Consider following row-filter expression that refers to a user attribute:
> {code:java}
> dept = ${{USER.dept}}{code}
>
> For this expression to evaluate correctly, all users who run query on the
> table should have an attribute named dept. To handle users for whom this
> attribute is not defined, an additional policy-item would be required, as
> shown below:
> {noformat}
> 1. "condition": "!HAS_USER_ATTR('dept')", "filterExpr": "dept = -1"
>
> 2. "filterExpr": "dept = ${{USER.dept}}"{noformat}
>
> Ability to use a default value when the attribute doesn't exist will
> eliminate the need for the additional policy item, like:
> {noformat}
> "filterExpr": "dept = ${{GET_USER_ATTR('dept', -1)}}{noformat}
>
> Added following macros to support optional default value:
>
> ||Macro||With default value||Description||Example return value||
> |GET_TAG_NAMES()|GET_TAG_NAMES('none')|Names of tags associated with the
> resource, separated by a comma|PII,PCI|
> |GET_TAG_ATTR_NAMES()|GET_TAG_ATTR_NAMES('none')|Names of attributes in tags
> associated
> with the resource, separated by a comma|piiType,score|
> |GET_TAG_ATTR('score')|GET_TAG_ATTR('score', 0)|Attribute value in tags
> associated with the
> resource, separated by a comma|0|
> |GET_UG_NAMES()|GET_UG_NAMES('none')|Names of groups the user belongs to,
> separated by a comma|analyst,manager|
> |GET_UG_ATTR_NAMES()|GET_UG_ATTR_NAMES('none')|Names of all attributes in
> groups the user
> belongs to, separated by a comma|dept,site|
> |GET_UG_ATTR('site')|GET_UG_ATTR('site', 'none')|Attribute value in groups
> the user belongs
> to, separated by a comma|10,20|
> |GET_UR_NAMES()|GET_UR_NAMES('none')|Names of roles assigned to the user,
> separated by a comma|data-steward,admin|
> |GET_USER_ATTR_NAMES()|GET_USER_ATTR_NAMES('none')|Names of all attributes of
> the user,
> separated by a comma|name,email|
> |GET_USER_ATTR('email')|GET_USER_ATTR('email', 'none')|Value of user
> attribute|n...@domain.com|
>
> For each macro listed above, there is another version with *_Q* added to the
> name, like:
> {code:java}
> GET_TAG_NAMES_Q(){code}
> These macros would quote each value, like:
> {code:java}
> 'PII','PCI'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4717) Skip showing 'Page not found' for wrong value is provided to a api parameter in Login Session Tab
[ https://issues.apache.org/jira/browse/RANGER-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4717: Attachment: 0001-RANGER-4717.patch > Skip showing 'Page not found' for wrong value is provided to a api parameter > in Login Session Tab > - > > Key: RANGER-4717 > URL: https://issues.apache.org/jira/browse/RANGER-4717 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4717.patch > > > From server side the api used in Audit Login Sessions Tab - > "/service/xusers/authSessions" has added a validation to requestIP api query > parameter. > When user enter text value a 'page not found' is shown. Need to skip showing > 'page not found' page for such scenario and show the server-side response as > an alert on Login Session Tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4718) Skip showing 'Page not found' page for INVALID_INPUT_DATA validation in User Profile
[ https://issues.apache.org/jira/browse/RANGER-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4718: Attachment: 0001-RANGER-4718.patch > Skip showing 'Page not found' page for INVALID_INPUT_DATA validation in User > Profile > > > Key: RANGER-4718 > URL: https://issues.apache.org/jira/browse/RANGER-4718 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4718.patch > > > When user provides invalid form values during profile update, the Ranger > React UI shows 'Page not found' page. Need to skip showing 'Page not found' > page for such scenario and show the server-side response as an alert on User > Profile page. > Also taking care of a minor issue, where email address is getting reset to > empty at a time of password change on User Profile page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4717) Skip showing 'Page not found' for wrong value is provided to a api parameter in Login Session Tab
[ https://issues.apache.org/jira/browse/RANGER-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4717: Description: >From server side the api used in Audit Login Sessions Tab - >"/service/xusers/authSessions" has added a validation to requestIP api query >parameter. When user enter text value a 'page not found' is shown. Need to skip showing 'page not found' page for such scenario and show the server-side response as an alert on Login Session Tab. was: >From server side the api used in Audit Login Sessions Tab - >"/service/xusers/authSessions" has added a validation to requestIP api query >parameter. When user enter text value a 'page not found' is shown. Need to skip showing 'page not found' page for such scenario and show the server-side response in as an alert on Login Session Tab. > Skip showing 'Page not found' for wrong value is provided to a api parameter > in Login Session Tab > - > > Key: RANGER-4717 > URL: https://issues.apache.org/jira/browse/RANGER-4717 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: ranger-react > > From server side the api used in Audit Login Sessions Tab - > "/service/xusers/authSessions" has added a validation to requestIP api query > parameter. > When user enter text value a 'page not found' is shown. Need to skip showing > 'page not found' page for such scenario and show the server-side response as > an alert on Login Session Tab. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4718) Skip showing 'Page not found' page for INVALID_INPUT_DATA validation in User Profile
Mugdha Varadkar created RANGER-4718: --- Summary: Skip showing 'Page not found' page for INVALID_INPUT_DATA validation in User Profile Key: RANGER-4718 URL: https://issues.apache.org/jira/browse/RANGER-4718 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar When user provides invalid form values during profile update, the Ranger React UI shows 'Page not found' page. Need to skip showing 'Page not found' page for such scenario and show the server-side response as an alert on User Profile page. Also taking care of a minor issue, where email address is getting reset to empty at a time of password change on User Profile page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4700) Audit logs for Masking policy is missing data mask type entry
[ https://issues.apache.org/jira/browse/RANGER-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4700: Attachment: 0001-RANGER-4700.patch > Audit logs for Masking policy is missing data mask type entry > - > > Key: RANGER-4700 > URL: https://issues.apache.org/jira/browse/RANGER-4700 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4700.patch > > > Audit logs for Masking policy is missing data mask type entry. > *Current Behaviour :-* > * Audit logs for Masking policy is missing data mask type entry for having > datamasklabel > other than "Custom". > *Steps to repro :-* > 1) Inside Hive service, navigate hive masking policy listing page. > 2) Click on "Add New Policy", add all the details. Under policy item section > add select masking option. Now save the policy > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > 4) Under "Masking Policy Items" table we would not see Data mask Types > details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3997) option to use default value when user/group/tag does not have the attribute
[
https://issues.apache.org/jira/browse/RANGER-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817648#comment-17817648
]
Himanshu Maurya commented on RANGER-3997:
-
Hi [~madhan],
While using GET_USER_ATTR('state', 'null') in policy condition I have 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=639,height=372!
!Screenshot 2024-02-15 at 5.20.36 PM.png|width=640,height=111!
!Screenshot 2024-02-15 at 5.27.54 PM.png|width=635,height=174!
Thanks and Regards
> option to use default value when user/group/tag does not have the attribute
> ---
>
> Key: RANGER-3997
> URL: https://issues.apache.org/jira/browse/RANGER-3997
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3997.patch, 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
>
>
> Consider following row-filter expression that refers to a user attribute:
> {code:java}
> dept = ${{USER.dept}}{code}
>
> For this expression to evaluate correctly, all users who run query on the
> table should have an attribute named dept. To handle users for whom this
> attribute is not defined, an additional policy-item would be required, as
> shown below:
> {noformat}
> 1. "condition": "!HAS_USER_ATTR('dept')", "filterExpr": "dept = -1"
>
> 2. "filterExpr": "dept = ${{USER.dept}}"{noformat}
>
> Ability to use a default value when the attribute doesn't exist will
> eliminate the need for the additional policy item, like:
> {noformat}
> "filterExpr": "dept = ${{GET_USER_ATTR('dept', -1)}}{noformat}
>
> Added following macros to support optional default value:
>
> ||Macro||With default value||Description||Example return value||
> |GET_TAG_NAMES()|GET_TAG_NAMES('none')|Names of tags associated with the
> resource, separated by a comma|PII,PCI|
> |GET_TAG_ATTR_NAMES()|GET_TAG_ATTR_NAMES('none')|Names of attributes in tags
> associated
> with the resource, separated by a comma|piiType,score|
> |GET_TAG_ATTR('score')|GET_TAG_ATTR('score', 0)|Attribute value in tags
> associated with the
> resource, separated by a comma|0|
> |GET_UG_NAMES()|GET_UG_NAMES('none')|Names of groups the user belongs to,
> separated by a comma|analyst,manager|
> |GET_UG_ATTR_NAMES()|GET_UG_ATTR_NAMES('none')|Names of all attributes in
> groups the user
> belongs to, separated by a comma|dept,site|
> |GET_UG_ATTR('site')|GET_UG_ATTR('site', 'none')|Attribute value in groups
> the user belongs
> to, separated by a comma|10,20|
> |GET_UR_NAMES()|GET_UR_NAMES('none')|Names of roles assigned to the user,
> separated by a comma|data-steward,admin|
> |GET_USER_ATTR_NAMES()|GET_USER_ATTR_NAMES('none')|Names of all attributes of
> the user,
> separated by a comma|name,email|
> |GET_USER_ATTR('email')|GET_USER_ATTR('email', 'none')|Value of user
> attribute|n...@domain.com|
>
> For each macro listed above, there is another version with *_Q* added to the
> name, like:
> {code:java}
> GET_TAG_NAMES_Q(){code}
> These macros would quote each value, like:
> {code:java}
> 'PII','PCI'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3997) option to use default value when user/group/tag does not have the attribute
[
https://issues.apache.org/jira/browse/RANGER-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Maurya updated RANGER-3997:
Attachment: Screenshot 2024-02-15 at 5.27.54 PM.png
Screenshot 2024-02-15 at 5.20.36 PM.png
Screenshot 2024-02-15 at 5.07.02 PM.png
> option to use default value when user/group/tag does not have the attribute
> ---
>
> Key: RANGER-3997
> URL: https://issues.apache.org/jira/browse/RANGER-3997
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-3997.patch, 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
>
>
> Consider following row-filter expression that refers to a user attribute:
> {code:java}
> dept = ${{USER.dept}}{code}
>
> For this expression to evaluate correctly, all users who run query on the
> table should have an attribute named dept. To handle users for whom this
> attribute is not defined, an additional policy-item would be required, as
> shown below:
> {noformat}
> 1. "condition": "!HAS_USER_ATTR('dept')", "filterExpr": "dept = -1"
>
> 2. "filterExpr": "dept = ${{USER.dept}}"{noformat}
>
> Ability to use a default value when the attribute doesn't exist will
> eliminate the need for the additional policy item, like:
> {noformat}
> "filterExpr": "dept = ${{GET_USER_ATTR('dept', -1)}}{noformat}
>
> Added following macros to support optional default value:
>
> ||Macro||With default value||Description||Example return value||
> |GET_TAG_NAMES()|GET_TAG_NAMES('none')|Names of tags associated with the
> resource, separated by a comma|PII,PCI|
> |GET_TAG_ATTR_NAMES()|GET_TAG_ATTR_NAMES('none')|Names of attributes in tags
> associated
> with the resource, separated by a comma|piiType,score|
> |GET_TAG_ATTR('score')|GET_TAG_ATTR('score', 0)|Attribute value in tags
> associated with the
> resource, separated by a comma|0|
> |GET_UG_NAMES()|GET_UG_NAMES('none')|Names of groups the user belongs to,
> separated by a comma|analyst,manager|
> |GET_UG_ATTR_NAMES()|GET_UG_ATTR_NAMES('none')|Names of all attributes in
> groups the user
> belongs to, separated by a comma|dept,site|
> |GET_UG_ATTR('site')|GET_UG_ATTR('site', 'none')|Attribute value in groups
> the user belongs
> to, separated by a comma|10,20|
> |GET_UR_NAMES()|GET_UR_NAMES('none')|Names of roles assigned to the user,
> separated by a comma|data-steward,admin|
> |GET_USER_ATTR_NAMES()|GET_USER_ATTR_NAMES('none')|Names of all attributes of
> the user,
> separated by a comma|name,email|
> |GET_USER_ATTR('email')|GET_USER_ATTR('email', 'none')|Value of user
> attribute|n...@domain.com|
>
> For each macro listed above, there is another version with *_Q* added to the
> name, like:
> {code:java}
> GET_TAG_NAMES_Q(){code}
> These macros would quote each value, like:
> {code:java}
> 'PII','PCI'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4687) Updating the "Something went wrong" page in Ranger React UI
[ https://issues.apache.org/jira/browse/RANGER-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4687: Attachment: 0002-RANGER-4687.patch > Updating the "Something went wrong" page in Ranger React UI > > > Key: RANGER-4687 > URL: https://issues.apache.org/jira/browse/RANGER-4687 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4687.patch, 0002-RANGER-4687.patch > > > Updating the "Something went wrong" page in Ranger React UI > *Current behaviour:-* > * If there's an error or code break in Ranger react file, the "Something > went wrong" page appears. > * The error details, including stack traces, are only shown in UI, this > makes the RANGER UI not available. > The error details, shouldn't be display in UI, instead of it add the buttons > for reloading and go to profile page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4692) Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)
[ https://issues.apache.org/jira/browse/RANGER-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta updated RANGER-4692: - Attachment: 0001-RANGER-4692.patch > Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation) > -- > > Key: RANGER-4692 > URL: https://issues.apache.org/jira/browse/RANGER-4692 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > Attachments: 0001-RANGER-4692.patch > > > Currently there are different type like (Policy, Role, Tag, UserStore and > GDS) on plugin status. > when we have plugins(large enough to accommodate in single page), It will be > helpful to identify any out-of-sync plugins based on download times, sorting > them by policyDownloadTime, tagDownloadTime, roleDownloadTime, > userstoreDownloadTime and gdsDownloadTime. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4692) Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)
[ https://issues.apache.org/jira/browse/RANGER-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Gupta updated RANGER-4692: - Description: Currently there are different type like (Policy, Role, Tag, UserStore and GDS) on plugin status. when we have plugins(large enough to accommodate in single page), It will be helpful to identify any out-of-sync plugins based on download times, sorting them by policyDownloadTime, tagDownloadTime, roleDownloadTime, userstoreDownloadTime and gdsDownloadTime. was: Currently there are different type like (Policy, Role, Tag, and GDS) on plugin status. when we have plugins(large enough to accommodate in single page), It will be helpful to identify any out-of-sync plugins based on download times, sorting them by policyDownloadTime, tagDownloadTime, roleDownloadTime and gdsDownloadTime. > Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation) > -- > > Key: RANGER-4692 > URL: https://issues.apache.org/jira/browse/RANGER-4692 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > > Currently there are different type like (Policy, Role, Tag, UserStore and > GDS) on plugin status. > when we have plugins(large enough to accommodate in single page), It will be > helpful to identify any out-of-sync plugins based on download times, sorting > them by policyDownloadTime, tagDownloadTime, roleDownloadTime, > userstoreDownloadTime and gdsDownloadTime. -- This message was sent by Atlassian Jira (v8.20.10#820010)
