Validation URI JSP files do not work when uploaded to the secured JSP Pages section in RSA Identity Governance & Lifecycle
Originally Published: 2019-10-09
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.1.1
Issue
In RSA Identity Governance & Lifecycle request forms, validation URIs that point to JSPs in the non-secured (external) area work as expected. However, if the validation URIs point to JSPs in the secured area, they fail to validate the input.
The example below illustrates this issue. A JSP file called numeric_validate.jsp has been created to validate that the input to a request form text field be a number. This JSP file has been uploaded to both the secure area and the external area. The request form text field has a validation URI that points to the JSP file. When the validation URI points to the JSP file uploaded to the external area, the validation occurs. When the validation URI points to the JSP file uploaded to the secure area, the validation fails.
<%
String value = request.getParameter("value");
if (!value.matches("[0-9]+")) {
out.println("Not a number!!");
}
%>
The JSP file has been uploaded to both the secure (JSP Pages) and external (External JSP Pages) areas:
A request form has been defined with a single text field.
Note that the text field has a validation URI defined that points to the JSP stored in the external area. This validation occurs correctly.
However, when the validation URI is modified to point to the JSP file stored in the secure area, the validation does not occur and the user is redirected to the home page.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P03
- RSA Identity Governance & Lifecycle 7.2
