[RANGER-278] REST, Store: validation of policy/service/service-def

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Assignee: Alok Lal
• Reporter: Alok Lal
• Created: 01/Mar/15 02:23
• Updated: 28/Apr/15 06:10
• Resolved: 28/Apr/15 06:10

Description

Policy/Service/ServiceDef validation should be added during create/update/delete operation. Here are some of the validations to add:

• values are provided for all mandatory fields (names, resources, etc)
• values are valid (for example: based on validationRegEx in the resource def, enum values, no duplicate names for service-def/service/policy-within-a-service)
• ensure that user has permissions to create/update/view policy/service/service-def
• check for conflicting/overlapping policies

Issue Links

• is cloned by: RANGER-324 Phase-II - REST, Store: validation of policy/service/service-def

Sub-Tasks

• service validations: make components either completely stateless or stateful by moving ctor arguments around: Resolved
• Allow updating a service's and policy's name and enforce name-uniqueness during their create/update: Resolved
• Service def validation: create/update/delete of service def should be validated.: Resolved
• All validations: review various string comparisons and change those that should be done in a case insensitive manner: Resolved
• Service: validate the recursiveSupported and excludesSupported values: Resolved