Environment
Novell Access Manager 3.1 SP3 IR1 Linux Access Gateway
Appliance
Novell Access Manager 3.1 SP3 IR1 Linux Access Gateway Service
Form Fill Policies
Novell Access Manager 3.1 SP3 IR1 Linux Access Gateway Service
Form Fill Policies
Situation
Purpose:
Configure a Form Fill policy to complete and and auto-submit an HTML form where a statement like the following is present in the source code:
input type="submit" id="submit-test" name="submit-test" value="Submit Form"...
Symptoms:
Given the same Form Fill policy and login page HTML source code, Linux Access Gateway Service (MAG) and Linux Access Gateway Appliance (LAG) shown to have different behaviors.
Having the "Auto Submit" enabled in the configured Form Fill policy, the LAG adds automatically the submit tag value to the posted data, while the MAG does not automatically post the submit tag value.
Based on the previous sample statement, LAG will add "submit-test=Submit Form" to the posted data while MAG will not.
The MAG behavior could cause login loops where the back-end applications check for the submit value to be posted, and in case is not, would present again the same exact login page.
Configure a Form Fill policy to complete and and auto-submit an HTML form where a statement like the following is present in the source code:
input type="submit" id="submit-test" name="submit-test" value="Submit Form"...
Symptoms:
Given the same Form Fill policy and login page HTML source code, Linux Access Gateway Service (MAG) and Linux Access Gateway Appliance (LAG) shown to have different behaviors.
Having the "Auto Submit" enabled in the configured Form Fill policy, the LAG adds automatically the submit tag value to the posted data, while the MAG does not automatically post the submit tag value.
Based on the previous sample statement, LAG will add "submit-test=Submit Form" to the posted data while MAG will not.
The MAG behavior could cause login loops where the back-end applications check for the submit value to be posted, and in case is not, would present again the same exact login page.
Resolution
The issue has been fixed in NAM 3.2.
Workaround:
A possible workaround is to add and extra Field in the Form Fill policy configuration to force the post of the submit tag as needed from the back end application.
Workaround:
A possible workaround is to add and extra Field in the Form Fill policy configuration to force the post of the submit tag as needed from the back end application.