[RANGER-3883] emailchange and passwordchange User REST API's work even when invalid user id is used in the url

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0, 2.4.0
• Component/s: Ranger
• Assignee: Ramachandran
• Reporter: Abhishek
• Created: 29/Aug/22 17:21
• Updated: 14/Apr/23 13:46
• Resolved: 02/Dec/22 19:22

Description

When a POST request is made to the following APIs return 200 status code even when the userId is invalid .

1. {RANGER_ADMIN_URL}

   /service/users/{USER_ID}/passwordchange

1.  {RANGER_ADMIN_URL}/service/users/{USER_ID}/emailchange

Ideally, the API's must return 404 not found when using an invalid userid in the url,
but in the case of the aforementioned APIs, POST request results in status code 200.

Issue Links

• causes: RANGER-4112 Update servicedef by name results in 400 status code while the same request works with update servicedef using id
• causes: RANGER-4188 updatePolicy results in 400 status code