Trousbleshooting Novell Access manager FormFill issues on the Linux Access Gateway

  • 3508988
  • 03-Dec-2007
  • 26-Apr-2012

Environment

Novell Access Manager 3
Novell Access manager 3 Service Pack 1

Resolution

1. FormFill will not start if the HTML structure of a document is broken

  1.1 missing "<HTML></HTML>" tags

Solution:
  • use a rewriter policy to add the missing entries.
  • make sure the policy is executed before the default rewrite policy
    or correct the source of the page on the web application server
Example:

use a character rewriter with the following string rewriting statements:
  • Search: </BODY>
  • Replace With:</BODY></HTML>
1.2 missing"<form>" or "</form>" tags

Solution:
  • use a rewriter policy to add the missing entries.
  • make sure the policy is executed before the default rewrite policy
    or correct the source of the page on the web application server

2. FormFill will not write any new shared secret credentials if the action attribute value on the HTML form tag is assigned to a JavaScript.
    Note: it will make use of credentials which are already stored

Example:

"name="e_login_main_start"
onSubmit="return verify(this,thisPage.isSubmitToSelf);"
action="javascript:trySubmit
'e_login_main_process.do','true','','e_login_main_start','submit1',null,'top=20,left=20,alwaysRaised=1,
scrollbars=0,width=550,height=550','post'); void(0);"
method="post">"

3. FormFill does not run an Auto Post if no method attribute has been defined in the Form tag

Example:

.........................
<form NAME="loginForm">
........................

Solution:
  • use a rewriter policy to add the missing entries.
  • make sure the policy is executed before the default rewrite policy
    or correct the source of the page on the web application server -
Example:
  • Search:<form
  • Replace With:<form method="get"

4. FormFill does not fill the OPTION element if the source page does not have a value attribute assigned

Example:
       " .........................
        <form action="select.htm">
        <select name="top2">
            <option>Bob</option>
            <option>Alice</option>
        </select>
        </form>
        ........................"

Solution:
  • change the source page in order to assign a valid OPTIOn attribute value
  • make sure the policy is executed before the default rewrite policy
    or correct the source of the page on the web application server -

Example:

"........................................................................
<form action="select.htm">
        <select name="top2">
            <option value="name1">Bob</option>
            <option value="name2">Alice</option>
        </select>
        </form>
 .................................................................................."

Additional Information

Form Fill is a function of the proxy rather than the ESP (which logs to catalina.out)
  • set the "LOG_LEVEL” entry from "5” (default) to "7” in the "/etc/laglogs.conf” file
  • run "tail -f /var/log/ics_dyn.log | grep 504507”