From 8a605be505a03a8b692dfea02905cda9eac63c70 Mon Sep 17 00:00:00 2001 From: Rakesh Gupta Date: Fri, 3 Jan 2025 18:00:16 +0530 Subject: [PATCH] RANGER-5089: Getting 204 instead of 404 status code when invalid service name is passed Signed-off-by: Dineshkumar Yadav --- .../main/java/org/apache/ranger/rest/XUserREST.java | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java b/security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java index 9f7e79f7f5..020cf61847 100755 --- a/security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java +++ b/security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java @@ -1489,6 +1489,16 @@ public RangerUserStore getSecureRangerUserStoreIfUpdated(@PathParam("serviceName Long downloadedVersion = null; boolean isValid = false; + try { + isValid = serviceUtil.isValidService(serviceName, request); + } catch (WebApplicationException webException) { + httpCode = webException.getResponse().getStatus(); + logMsg = webException.getResponse().getEntity().toString(); + } catch (Exception e) { + httpCode = HttpServletResponse.SC_BAD_REQUEST; + logMsg = e.getMessage(); + } + try { XXService xService = rangerDaoManager.getXXService().findByName(serviceName); if (xService != null) {