Gautam Borad created RANGER-426:
-----------------------------------
Summary: Ranger KMS policy not matching the right resource name
Key: RANGER-426
URL: https://issues.apache.org/jira/browse/RANGER-426
Project: Ranger
Issue Type: Bug
Affects Versions: 0.5.0
Reporter: Gautam Borad
Assignee: Gautam Borad
Fix For: 0.5.0
Steps to reproduce :
# Create a ranger kms policy with keyname as test*
# Provide create_key permission to the testuser
# Execute hadoop key create command as the testuser (with a keyname test1)
+Expected result:+ Key should be created
+Actual result:+ Key is not created, failing with error message user does not
have permission.
Issue seems to be caused by resource_name is calculated wrongly and apparently
"kms" comes as the resource name for all requests. Verified this via audit page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
