Description
If we create a policy with non-existing permissions through curl then, it gets created successfully but has an impact on UI as permission module goes in the loading state.
Example:
in hive's row-level-filtering there is no 'update' permission in Access. If we create a policy with 'select' and 'update' in Access then it allows us to create a policy(returns response code 204) but ranger-ui permission module shows loading icon
Attachments
Attachments
Issue Links
- links to