[RANGER-4112] Update servicedef by name results in 400 status code while the same request works with update servicedef using id

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0, 2.4.0
• Fix Version/s: 3.0.0, 2.4.0
• Component/s: Ranger
• Assignee: Pradeep Agrawal
• Reporter: Abhishek
• Created: 28/Feb/23 09:31
• Updated: 14/Apr/23 13:45
• Resolved: 02/Mar/23 05:59

Description

If a PUT request is made to update the servicedef by id (BASE_URL/service/public/v2/api/servicedef/id), the request passes,
but if the same PUT request is made to update the servicedef by name (BASE_URL/service/public/v2/api/servicedef/name/{servicedef_name}), then it results in 400 Bad request.

Issue Links

• is caused by: RANGER-3883 emailchange and passwordchange User REST API's work even when invalid user id is used in the url
• is cloned by: RANGER-4188 updatePolicy results in 400 status code
• links to: Review request link