Environment
Novell Access Manager 3.1 Linux Access Gateway
Siebel 7.7 running on back end Web server
Siebel 7.7 running on back end Web server
Situation
Access Manager setup with a Linux Access Gateway (LAG) accelerating a number of back end Web servers. Single sign of to these Web servers are provided through a number of formfill and Identity Injection policies, and work fine with the exception of one Siebel application. When using formfill to populate the Siebel login form, the users found that the users credentials were not submitted to the Proxy. The end result is that users could not single sign of to the Siebel application through the LAG.
Resolution
Modify the formfill policy so that the following entry is added to the 'Javascript to
execute on submit:' field.
<script language="JavaScript">
<script language="JavaScript">
<!--
function executeJavaScript()
{
var
frm = document.forms.SWEEntryForm;
var ff =
document.createElement("INPUT");
ff.type="hidden";
ff.name="SWECmd";
ff.value="ExecuteLogin";
frm.appendChild(ff);
var ff =
document.createElement("INPUT");
ff.type="submit";
ff.name="altSubmit";
ff.id="altSubmit";
ff.value="Login";
frm.appendChild(ff);
document.getElementById('altSubmit').click();
return true;
}
function
LAGSubmitForm()
{
executeJavaScript();
}
//-->
</script>
Additional Information
The form returned by the LAG to the browser could never be submitted because one of the elements of the form is
named "submit". The solution above works around this conflict with additional javascript.
It is possible that the elements may be different at other customer sites running different versions of Siebel. The proper procedure of looking at the Source code of the Login Form page should be done and the header traced from browser on submitting successful credentials and to sure appropriate adjustment is made to the FF policy.
It is possible that the elements may be different at other customer sites running different versions of Siebel. The proper procedure of looking at the Source code of the Login Form page should be done and the header traced from browser on submitting successful credentials and to sure appropriate adjustment is made to the FF policy.