RANGER-5089: Getting 204 instead of 404 status code when invalid service name is passed

Signed-off-by: Dineshkumar Yadav <dineshkumar.yadav@outlook.com>

security-admin/src/main/java/org/apache/ranger/rest/XUserREST.java

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 9f7e79f..020cf61 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
@@ -1490,6 +1490,16 @@ public RangerUserStore getSecureRangerUserStoreIfUpdated(@PathParam("serviceName
 
 		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) {
 				isValid = true;