Difference between InPlaceSilent enabled and InPlaceSilentPolicyDoesSubmit advanced options

  • 7010956
  • 18-Oct-2012
  • 18-Oct-2012

Environment

NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 Access Gateway
Formfill enabled

Situation

Two advanced options that effect form fill policy are documented here:

https://www.netiq.com/documentation/novellaccessmanager32/accessgatewayhelp/data/agsglobaladv.html

#NAGGlobalOptions InPlaceSilent: This enables single sign‐on to certain Web sites that require the login page to remain as is without any modifications to its structure. This option is equivalent to .enableInPlaceSilentFill in the 3.1 SP4 Access Gateway Appliance.

and

#NAGGlobalOptions InPlaceSilentPolicyDoesSubmit=on: This option should be used to fill forms with complex JavaScript or VBScripts. This option is equivalent to .enableInPlaceSilentFillNew in the 3.1 SP4 Access Gateway Appliance.

Is it possible to get more detail on precisely what these two options do?  Exactly what does the FF engine do or not do when these options are enabled?

Resolution

#NAGGlobalOptions InPlaceSilent: This advanced option will cause formfill to send back the HTML code from the web server and not do any javascript/function rewriting that we have in default mode. By default, it will only submit form[0] and nothing else. If you have additional forms you need submitting, this will fail.
 
#NAGGlobalOptions InPlaceSilentPolicyDoesSubmit=on: Used when additional (non form[0]) forms on page need to be handled and can add additional logic to be handled
 
Here's what I see in the http headers with
 
a) InPlaceSilent enabled and InPlaceSilentPolicyDoesSubmit disabled

function NAGPostForm()
{
executeJavaScript();
document.forms[0].submit();
}
NAGPostForm();
</script>
</body>
</html>
 
b) InPlaceSilent enabled and InPlaceSilentPolicyDoesSubmit enabled

function NAGPostForm()
{
executeJavaScript();
// Can add own stuff in here before document submitted
}
NAGPostForm();
</script>
</body>
</html>

Feedback service temporarily unavailable. For content questions or problems, please contact Support.