Environment
Novell Access Management 3 Linux Access Gateway
Access Manager 3 Support Pack 1 release Candidate 2 applied (3.0.1-207 build)
Situation
A web based application was front ended by the Linux Access
Gateway. A Formfill policy was created to insert string constants
into the various fields of the application login form.
When the users authenticated to the Identity server and hit the protected resource on the Linux Access Gateway that had the above formfill policy enabled, none of the fields were auto populated.
When the users authenticated to the Identity server and hit the protected resource on the Linux Access Gateway that had the above formfill policy enabled, none of the fields were auto populated.
Resolution
Add another dummy input field into the formfill policy with
Credential profile (see below) in cases where the Formfill policy
needs to fill the HTML form with only string constants. In cases
where string constants and other data (LDAP attributes) are
required in the form, all will work fine.
To add this additional "dummy" element input field, go to the formfill policy created. Under 'Fill Options', create a new entry where the input field name is anything you want but provide the
- 'Input field type' value as "text"
- 'Input field value' as "credential profile"
- Credential profile as "LDAP User name"
Once the policy is saved and applied, the formfill'ing of the login page will work ie. the strings will get added.
To add this additional "dummy" element input field, go to the formfill policy created. Under 'Fill Options', create a new entry where the input field name is anything you want but provide the
- 'Input field type' value as "text"
- 'Input field value' as "credential profile"
- Credential profile as "LDAP User name"
Once the policy is saved and applied, the formfill'ing of the login page will work ie. the strings will get added.
Additional Information
Looking at the catalina.out log file on the LAG, one could see that the LAG FF is
sending GetAttr Request to the eSP even when all the input elements
in the policy are configured to use String Constants and as no data would be
received in the response, she's treating it as the "DataNotAvailable" case and
is not filling the form.