Help : Call Login Module directly when iView is launched - without submit

Question

Hi there,
we have developed a login module on for our NW2004S SP13 Portal, that checks the IP address of the client to be in a valid range. If so, the standard SAP login screen must be bypassed. If not, the standard login screen needs to be shown (we use the standard sap umLogonPage, we only made a copy z.com.portal.runtime.logon.par) and added to the portalapp.xml an entry which is a copy of the 'certlogon' entry..
-> What we like to achieve is that the logonstack is called directly when the application is launched.
a) Code below functions, but only one problem : when the IP Address is invalid (login module returns false), a blank page is shown instead of the default userid / pw page.
    In case of valid IP OK, invalid IP (login module returns false) blank page :o(
b) As an alternatice, in my opinion, it would be best to use the standard SAP class in the portalapp.xml  (com.sap.sapportals.portal.ume.component.logon.SAPMLogonComponent) & have some sort of servlet in front
The behaviour of which page to return in case of failed logon is contained in com.sap.portal.runtime.logon_api.jar, class com.sap.sapportals.portal.ume.component.logon.SAPMLogonComponent -> class SAPMLogonLogic).
How can this be done? I've already cracked my head over it, but can't get this to work -
My coding for a) :
package z.x.sapportals.portal.ume.component.logon;
import com.sap.security.api.logon.ILogonFrontend;
import com.sapportals.portal.prt.component.AbstractPortalComponent;
import com.sapportals.portal.prt.component.IPortalComponentRequest;
import com.sapportals.portal.prt.component.IPortalComponentResponse;
import com.sapportals.portal.prt.session.IUserContext;
public class xSAPMLogonComponent extends AbstractPortalComponent     implements ILogonFrontend
     protected void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
          response.write("\n<!-- component context:" + request.getComponentContext().getComponentName() + "-->\n");
          response.write("<!-- class: " + getClass().getName() + "-->\n");
          String firstName ="";
          String lastName = "";
          String logonUid = "";
          String password = "";
          String authscheme = "";
          IUserContext userContext = request.getUser();
          if (userContext != null)
               firstName = userContext.getFirstName();
               lastName = userContext.getLastName();
               logonUid = userContext.getLogonUid();
               password = "dummy";
               authscheme = (String)request.getValue("com.sap.security.logon.authscheme.required");
               response.write("Welcome :");
               response.write("logonUid = " + logonUid + "<br><br>");
               response.write("j_password = " + password + "<br><br>");
               response.write("<form id=\"redirform\" method=\"post\" >");
               response.write("<input type=\"hidden\" name=\"login_submit\" value=\"on\">");
               response.write("<input type=\"hidden\" name=\"j_user\" value=\"" + logonUid + "\">");
               response.write("<input type=\"hidden\" name=\"j_password\" value=\"" + password + "\">");
               response.write("<input type=\"hidden\" name=\"j_authscheme\" value=\"" + authscheme + "\">");
               response.write("<input type=\"submit\" value=\"send\">");
               response.write("</form>");
//                      Commented out javascript auto submit to press submit manually for testing
     /* (non-Javadoc)
@see com.sap.security.api.logon.ILogonFrontend#getTarget()
     public Object getTarget()
          // TODO Auto-generated method stub
          return this;
     /* (non-Javadoc)
@see com.sap.security.api.logon.ILogonFrontend#getType()
     public int getType() {
          // TODO Auto-generated method stub
          return 2;
Portalapp.xml :
    <component name="iplogon">
      <component-config>
        <property name="ClassName" value="z.x.sapportals.portal.ume.component.logon.xSAPMLogonComponent"/>
        <property name="SafetyLevel" value="no_safety"/>
        <property name="LocalModeAllowed" value="true"/>
      </component-config>
      <component-profile>
        <property name="AuthScheme" value="anonymous"/>
        <property name="com.sap.portal.pcm.Category" value="platform">
          <property name="inheritance" value="final"/>
        </property>
        <property name="SupportedUserAgents" value="(MSIE, >=5.0, *) (Netscape, *, ) (Mozilla,,*)">
          <property name="inheritance" value="final"/>
        </property>
      </component-profile>
    </component>
authschemes.xml
        <authscheme name="iplogon">
            <authentication-template>
                radiusExtended
            </authentication-template>
            <priority>22</priority>
            <frontendtype>2</frontendtype>
            <frontendtarget>z.x.portal.runtime.logon.iplogon</frontendtarget>
        </authscheme>

Answer 1

Hi,
I'm not sure if you have already solved this issue, I was looking up another issue and came across this topic, maybe I can close this topic for you.....
Here is what you could do...
1) Create a custom login module stack with your login module
2) Create a authentication scheme that refers this stack
  For example, you have defined a login module stack called certlogon in the Security Provider service in the Visual Administrator. You   want to create an authentication scheme that uses this login module stack. To do this, you add the following excerpt to the authschemes.xmlfile.
<authscheme name="myauthscheme">
      <!-- multiple login modules can be defined -->
      <authentication-template>
        certlogon
      </authentication-template>
      <priority>20</priority>
      <!-- the frontendtype TARGET_FORWARD = 0 -->
      <!-- TARGET_REDIRECT = 1, TARGET_JAVAIVIEW = 2 -->
      <frontendtype>2</frontendtype>
      <!-- target object -->
      <frontendtarget>
        com.mycompany.certlogonapp
      </frontendtarget>
  </authscheme>
In this schema refer your custom login application.
thanks,
Sudhir