Troubleshooting "Input validation error. Please Contact Support"

Troubleshooting "Input validation error. Please Contact Support"

In this article  :

  • Issue description

  • Prerequisites

  • Possible causes

  • Resolution

  • How to reach support

  • Related topics and articles

 Issue description   

When a customer attempts to perform an action in ADAudit Plus such as saving a configuration, performing a search, or initiating any general action the following error message may appear:

Message:"Input validation error. Please Contact Support"

In some cases, the error may appear in another language as: "adap_input_val_err", which refers to the same issue.

Note: Issues related to input validation errors fixed in earlier builds. So if the product is in older build upgrading to the latest build will fix the issue.

Example serverOut log entry:

To locate the issue, search for "IAMSecurityException ErrorCode" in the serverOut file for the date the issue occurred.

 Prerequisites   

  • Access to the ADAudit Plus installed server.

  • Permission to view and edit configuration files located in the <Installation Folder>\webapps\adap\WEB-INF\ directory.

  • Basic knowledge of using Inspect element > Network tab in a browser for troubleshooting.

 Possible causes   

  • Input validation issues in request handling due to missing or mismatched parameters.

  • Specific URLs not being correctly defined in security.xml or security-fw.xml.

  • A mismatch between product build configurations (e.g., older builds missing the required max-len property).

  • Multiple affected URLs not fully updated.

 Resolution   

Step 1: Identify the issue  

  1. Check serverOut logs for "IAMSecurityException ErrorCode".

  2. Locate the related URL from the logs (e.g., /api/json/ConfigureFileIntegrity/viewConfiguredServers).

Step 2: Update the configuration files  

  1. Navigate to: <Installation Folder>\webapps\adap\WEB-INF\security

  2. Open the security.xml file.

    • If the URL is not found here, also check in security-fw.xml.

Step 3: Apply required changes  

a. Add max-len="-1" (only for build 7110)
At line 10 in security.xml, update the following:

From:

<param name="[A-Za-z_]+" type="String" name-regex="true" max-occurrences="15" />

To:

<param name="[A-Za-z_]+" type="String" name-regex="true" max-occurrences="15" max-len="-1"/>  

Note: For builds later than 7110, this parameter is automatically added. You can skip this step.

b. Update the URL entry

From:

<url path="/api/json/ConfigureFileIntegrity/viewConfiguredServers" dynamic-params="false" csrf="true" method="post">
    <param name="params" type="JSONObject" max-len="-1" template="ConfiguredFIMJSON"/>
</url>

To:

<url path="/api/json/ConfigureFileIntegrity/viewConfiguredServers" dynamic-params="true" csrf="true" method="post" />

Step 4: Restart ADAudit Plus  

  • Restart the ADAudit Plus service.

  • Verify if the issue is resolved.

Step 5: Check for additional affected URLs  

  • If the issue persists, repeat the above steps for other related URLs found in logs.

  • Restart the service again once all changes are applied.

Alternate method (finding affected URL)  

If the log does not clearly show the URL, you can use the browser Inspect tool:

  1. Right-click in the browser and select Inspect element.

  2. Go to the Network tab.

  3. Repeat the action that caused the error.

  4. Look for a red-marked request (401).

  5. Click on it to identify the affected URL.

Related topics and articles  

How to reach support  

If the issue persists or you need help validating the JRE structure, contact the ManageEngine ADAudit Plus support team at support@adauditplus.com.

                  New to ADSelfService Plus?