[RANGER-426] Ranger KMS policy not matching the right resource name

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Assignee: Gautam Borad
• Reporter: Gautam Borad
• Created: 24/Apr/15 11:41
• Updated: 19/May/15 07:36
• Resolved: 19/May/15 07:36

Description

Steps to reproduce :

1. Create a ranger kms policy with keyname as test*
2. Provide create_key permission to the testuser
3. 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.

Issue Links

• links to: Review request link