You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhishek (Jira)" <ji...@apache.org> on 2023/07/11 13:15:00 UTC

[jira] [Created] (RANGER-4311) JSON response returned for user object contains empty fields

Abhishek created RANGER-4311:
--------------------------------

             Summary: JSON response returned for user object contains empty fields
                 Key: RANGER-4311
                 URL: https://issues.apache.org/jira/browse/RANGER-4311
             Project: Ranger
          Issue Type: Bug
          Components: Ranger
            Reporter: Abhishek


{color:#172b4d}In RANGER-3948, changes were done so that the response JSON object does not{color}
{color:#172b4d}contain empty fields.{color}
{color:#172b4d}For example, if the policy label field is empty, then the policy json will not contain the empty label fields "policyLabel".{color}
{color:#172b4d}Similarly, if a role is created with just a name, then the users and groups fields will not be returned when role details are fetched.{color}
{color:#172b4d}But if a user is fetched, two empty fields, groupIdList and groupNameList are returned{color}
{color:#172b4d}even if the user is not a part of any group.{color}{color:#172b4d}

If the role is fetched, the response does not contain the description if it is empty,
but the user/group object description is returned even if it is empty.

{color:#172b4d}Ideally, these fields should be removed if they are empty and not being used.{color}
{color}



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