Custom Logon PAR

Hello,
I am trying to access general information of logged in user from logon par file. For that I have created custom abstract portal component to access UME API and redirected umLogonPage.jsp to it.
My problem is after checking UME api user able to logged in to portal but it stuck in custom component.
Please help me out what am doing is right approach or is there any better way?
Thanking in advance.
Regards,
Pravin

Hi Pravin,
That was to retrieve user data thru java class and you can keep this retrieved user data inside a bean class and call the bean class from your jsp.
Otherwise, Pls try below code sample inside jsp -
<%
   IPortalComponentRequest currentRequest = (IPortalComponentRequest) pageContext.getAttribute(javax.servlet.jsp.PageContext.REQUEST);
  com.sap.security.api.IUser user = currentRequest.getUser();     
  String fName = user.getFirstName();
%>
Regards,
Sen

Similar Messages

  • Com.sap.portal.runtime.logon.par information in Authschemes.xml

    Hello Portal gurus,
        I am trying to customize the Portal logon page by modifying the com.sap.portal.runtime.logon.par file. I modified the par file. But after this change, I wanted to change the authschemes.xml file to reflect the par file changes.
    When I downloaded the .xml file, I only found occurences of <b><frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget></b>, <b><frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget></b> and  <b><frontendtarget>com.sap.portal.runtime.logon.header</frontendtarget></b>
    Could anybody confirm, whether I have to rename these occurrences of com.sap.portal.runtime.logon with my customized logon .par file name between <frontendtarget> and </frontendtarget>?
    Points will be awarded for correct answers and useful suggestions.
    Thanks,
    ~~LB

    Hi
    Here is the procedure
    1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
    2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
    3. Switch to edit mode by clicking on the pencil which is at the upper right area.
    4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
    5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
    project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Don’t remove the part behind it.
    (These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
    6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
    a.Select the node com.sap.security.core.ume.service.
    b. Choose the symbol for Creating a node below the selected node.
    c. Select the type File-entry.
    d. Choose Upload and select the custom file from your local directory.
    e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
    f. Choose Create.
    g. Choose “Close window”.
    h. The new node appears in the configuration tree.
    i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
    The value needs to be changed from authschemes.xml to authschemes_myHR.xml
    j. Restart the Portal. That is often not done and the changes will not appear.
    Rgds
    Srikanth

  • Custom Logon Page Error

    I created a custom logon page and its not working. I'm pretty sure that it has to do with the authscheme.xml file. Can someone post the authscheme.xml file they used for their custom logon page, or tell me what is wrong with mine. I posted it below and my custom logon par is named: CM_Logon.par.
    Really appreciate any help.
    Regards,
    Tom
      <?xml version="1.0" encoding="UTF-8" ?>
    - <!--   Configuration File for Authentication Schemes
      -->
    - <!--  $Id: //shared_tc/com.sapall.security/630_VAL_REL/src/_deploy/dist/configuration/shared/authschemes.xml#1 $ from $DateTime: 2004/03/08 16:48:43 $ ($Change: 14741 $)
      -->
    - <document>
    - <authschemes>
    - <!--   authschemes, the name of the node is used
      -->
    - <authscheme name="uidpwdlogon">
    - <!--  multiple login modules can be defined
      -->
      <authentication-template>ticket</authentication-template>
      <priority>20</priority>
    - <!--  the frontendtype TARGET_FORWARD = 0, TARGET_REDIRECT = 1, TARGET_JAVAIVIEW = 2
      -->
      <frontendtype>2</frontendtype>
    - <!--  target object
      -->
      <frontendtarget>CM_Logon.certlogon</frontendtarget>
      </authscheme>
    - <authscheme name="certlogon">
      <authentication-template>client_cert</authentication-template>
      <priority>21</priority>
      <frontendtype>2</frontendtype>
      <frontendtarget>CM_Logon.certlogon</frontendtarget>
      </authscheme>
    - <authscheme name="basicauthentication">
      <authentication-template>ticket</authentication-template>
      <priority>20</priority>
      <frontendtype>2</frontendtype>
      <frontendtarget>CM_Logon.basicauthentication</frontendtarget>
      </authscheme>
    - <authscheme name="header">
      <authentication-template>header</authentication-template>
      <priority>5</priority>
      <frontendtype>2</frontendtype>
      <frontendtarget>CM_Logon.header</frontendtarget>
      </authscheme>
    - <!--  Reserved 'anonymous' authscheme added for being in the list of authschemes
      -->
    - <authscheme name="anonymous">
      <priority>-1</priority>
      </authscheme>
      </authschemes>
    - <!--   References for Authentication Schemes, this section must be after authschemes
      -->
    - <authscheme-refs>
    - <authscheme-ref name="default">
      <authscheme>uidpwdlogon</authscheme>
      </authscheme-ref>
    - <authscheme-ref name="UserAdminScheme">
      <authscheme>uidpwdlogon</authscheme>
      </authscheme-ref>
      </authscheme-refs>
      </document>

    Venkat,
       Here is the only error message I can find in the server trace error log. This leads me to believe it is something to do with the authschemes.xml file.
    Thanks,
    Tom
    Time : 13:15:26:879
    Category : /System/Server
    Date : 07/18/2005
    Message : An error occured during authscheme computation.
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : Demo_LogonPage.certlogon
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:235)
         at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:154)
         at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)
         at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:276)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)
         at com.sap.portal.navigation.Gateway.service(Gateway.java:68)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component Demo_LogonPage.certlogon because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 35 more
    Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 39 more
    Severity : Error
    Location : com.sap.portal.portal
    Message ID : 000BCD9C959D00590000000F00001A400003FC2FBEF3AA88
    Thread : SAPEngine_Application_Thread[impl:3]_10
    Source Name : com.sap.portal.portal
    Datasource : 1121777405726:E:\usr\sap\EP6\JC00\j2ee\cluster\server0\log\defaultTrace.trc
    Application : sap.com/irj
    Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : Demo_LogonPage.certlogon
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:235)
         at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:154)
         at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)
         at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:276)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)
         at com.sap.portal.navigation.Gateway.service(Gateway.java:68)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component Demo_LogonPage.certlogon because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 35 more
    Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 39 more
    Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : Demo_LogonPage.certlogon
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:235)
         at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:154)
         at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)
         at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)
         at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:276)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:290)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:346)
         at com.sap.portal.navigation.Gateway.service(Gateway.java:68)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component Demo_LogonPage.certlogon because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
         at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
         at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
         ... 35 more
    Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 39 more
    Dsr Component :
    Dsr Transaction : 886750b0f7af11d9c469000bcd9c959d
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 92
    Source : com.sap.portal.portal
    ThreadObject : SAPEngine_Application_Thread[impl:3]_10
    Transaction :
    User : Guest

  • Portal Run time error after deploying custom logon page par file in portal

    Hi Experts,
       We have customized the standard portal logon par file for client XYZ and imported it with the same name (com.sap.portal.runtime.logon.par)  in portal.
       It is working fine for XYZ . And another client ABC wants the same customization for them also. So we took the par file from XYZ and imported it in ABC system. But in ABC system, we are getting Portal Run time Error. When we checked the logs, it is showing error in LogonBean class.Wwe have included the necesary jar files. Could anyone help us in identifying what is missing?
    Thanks
    VJ

    Hello Vijay,
    Please paste or attach the error log.
    Regards,
    Haseena

  • Custom logon's PAR w/config branding image and branding text.....

    Hi all,
    I have changed the configuration of  the logon's branding-image and branding-text through their properties on the config tool. With the standard logon all works fine, but I have customized the logon's PAR and I Have changed the authscheme.xml, and now, the images that i have changed don't appear  on the screen. I just want to know if there is a way to fix this changing only the properties on the config tool (as the stadard does) or as i have changed the standard logon's PAR to a Custom logon's PAR, I must manage this images within this new custom logon's PAR?. Please help, thanks for watching
    Regards,
    MC

    Images were missing on the relevant path (server filesystem) for custom logon's PAR. That´s all
    Regards
    MC

  • Problem With LOGON.par

    HI
    iam using NWDS 2.0.12 version as indicated i have moved the par file into the studio and edited the jsp tages according to my needs by  the system is showing the error
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    The exception was logged. Inform your system administrator..
    See the details for the exception ID in the log file
    The foloowing steps i followed
    The login page is part of the par file with the name com.sap.portal.runtime.logon.par
    1) Copy the file with the above name from the following location (EP6 SP9 and higher). It has the additional ending ">\<SID>\<Instance>\j2ee\cluster\server<#>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd\
    2) Import the PAR file into Netweaver Developer Studio:
    3)Edited the file
    4) while importing the lib directory was empty so i copied the files
    1. com.sap.portal.runtime.logon_api.jar
    2. umelogonbase.jar
    into the lib directory
    5) after that i made a par file using nwds and winzip.
    6)Then i changed the authescemes .xml file
    1. Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee\configtool\configtool.bat.
    2. Navigate to cluster_data>server>persistent>com.sap.security.core.ume.service.
    3. Switch to edit mode by clicking on the pencil which is at the upper right area.
    4. In the tree, select authschemes.xml and choose Download. Save the file to your local directory
    5. Edit the local file: To select the new PAR file as the Logon page change the occurrence of all substrings com.sap.portal.runtime.logon to your
    project/PAR file name. All com.sap.portal.runtime.logon should be substituted with something like com.company.portal.runtime.logon (or whatever you project name is). Don’t remove the part behind it.
    (These are the profiles in the portalapp.xml and have the names default, certlogon, basicauthentication, header, and anonymous).
    6. Create a new node in the configuration tree in the Config-Tool for the edited file as follows:
    a.Select the node com.sap.security.core.ume.service.
    b. Choose the symbol for Creating a node below the selected node.
    c. Select the type File-entry.
    d. Choose Upload and select the custom file from your local directory.
    e. Enter a name for the entry, for example, authschemes_myHR.xml. By default, the name of the uploaded file is used.
    f. Choose Create.
    g. Choose “Close window”.
    h. The new node appears in the configuration tree.
    i. Go to Global server configuration>services> com.sap.security.core.ume.service and edit the property login.authschemes.definition.file.
    The value needs to be changed from authschemes.xml to authschemes_myHR.xml
    j. Restart the Portal. That is often not done and the changes will not appear.
    after doing all this the portal shows an error
    can anyone tel me where am i going wrong what steps iam missing while changing the par file.aslo pls if any one can tel me where exacty the log file is stored and how do i check the exception id.

    Hi Pankaj,
    The steps seem to be correct.
    The physical location of the log file is:
    \usr\sap\<instance name>\JC01\j2ee\cluster\server0\log
    You could check in the defaultTrace files here. Also note that the log entry could go into the Trace files in one of the Server in the clusters.
    You could also look for the Log file from within the portal using Java Home-> Portal Log Viewer -> give the Exception id in the search
    Regards,
    Ashwini.

  • Custom Logon Screen (Branding)

    Hi All,
    We want to chagne the WebDynpro login screen to achieve the following:
    - Custom Logo
    - Change Password functionality.
    I've located the login war file.
    com.sap.security.core.logon.war that contains the logon screen and have changed the JSP accordingly and it has worked.
    Does anyone know of a better way to change this?
    Regards,
    Michael

    Hi,
    The actual way of doing the Branding is as follows
    1. get the com.sap.portal.runtime.logon.par.bak in the irj deployed folder.
    2. remove the .bak.
    3. import it in the NWDS, do the changes in the jsp pages of login, logout, etc.
    4. make the par
    5. upload the same
    6. if you change the par name and uploaded then u need to do the changes to the authscheme.xml in the configtool, configuration
    7. restart the server.
    8. your changes are done.
    PS: Please take the com.sap.portal.runtime.logon.par.bak backup, if you gone wrong., then do upload it
    Thanks & Regards,
    Ragahvendra Pothula

  • Problem in JNDI Lookup of Deployable Proxy inside logon.par

    Hi,
    I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
    <b>from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().</b>
    I am calling a Deployable Proxy in that method by using the below code,
    <b>Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
    MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);</b>
    objMailGatewayViDocument.sendMail(...);
    I am getting the Exception,
    <b>com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.</b>
    I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
    Please let me know the possible solutions where i can call a deployable proxy inside the logon par file.
    Thanks and Regards,
    Sekar

    Hi Sekar!
      Try this:
    MailGateway objMailGateway=(MailGateway)ctx.lookup
    ("wsclients/proxies/sap.com/MailProxy/com.ms.sap.sms.MailProxy/wsPort_Document");
      I have understood you're deploying a par file... if you are doing this way, don't forget to put a reference to the webservice in portalApp.xml:
      <property name="PrivateSharingReference" value="SAPJ2EE::sap.com/com.ms.sap.sms.MailProxy"/>
      Hope this can work.
      Are you sure this destination is the one you are looking for?
    sap.com/CHEPSMSProxy/com.ms.sap.sms.SMSProxy/wsPort_Document
      It seems to be anther app. If this is the correct app then the JNDI should be:
       MailGateway objMailGateway=(MailGateway)ctx.lookup
    ("wsclients/proxies/sap.com/CHEPSMSProxy/com.ms.sap.sms.SMSProxy/wsPort_Document");
      If this fails and if you have have source code of the proxy app, check out the application.xml file, and look for Display name. Also look for the application-j2ee-engine.xml file, and look for the 'Vendor name', and post them please.
      Eneko
    Message was edited by:
            Eneko Rodriguez

  • Problem in JNDI Lookup of Deployable Proxy from the logon par file

    Hi,
    I have customized the Logon par file and have a functionality to call a webservice when the Password Reset happens.
    <b>from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and  there is a method called performResetPassword().</b>
    I am calling a Deployable Proxy in that method by using the below code,
    <b>Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");                    
    MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
    objMailGatewayViDocument.sendMail(...);</b>
    I am getting the Exception,
    <b>com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MailProxy.</b>
    I have deployed the Deployable Proxy in the J2EE Engine and add this API Jar as the External Library (Project >Properties>Java Build Path ---> Add External jars...Added the .jar file generated in the Proxy Project).
    <b>Please let me know the possible solutions where i can call a deployable proxy inside the logon par file</b>.
    Thanks and Regards,
    Sekar

    Hi,
    I have fixed this error by changing the lookup as follows.
    InitialContext ctx=new InitialContext();
    Gateway objGateway=(Gateway)ctx.lookup("wsclients/proxies/sap.com/GatewayProxy/com.ms.sap..GatewayProxy");
    Just open Visual Administrator and look for the path under wsclients for proper naming.
    Thanks and Regards,
    Sekar
    Edited by: Sekar M on Jan 16, 2008 6:10 PM

  • Why custom logon error messages doesn't work in WAS 7.0, EP 7.0?

    I managed to get custom error messages in WAS 6.40 / EP 6.0.
    I'm using JAAS custom Login module for user authentication and from there different Login Exceptions are thrown.
    I have modified logon.par file to display different error messages like "Logon ID is empty", "Password is empty", "Your user ID or password could not be validated.  Please check and try again."
    When i copy the same code into my working environment i.e WAS 7.0 / EP 7.0, it doesn't work, message always was "User Authentication Failed". Do anyone knows the reason why i was like that?
    Can you please explain exactly when the custom login module gets executed after the user clicks on "Logon" Button.
    In logon.par file i have not seen any code to execute JAAS - custom logon module. PLease explain exact execution flow ..
    Thanks in advance ..
    MMK

    Your card reader might be finicky like mine. Figure out which device your card reader is at (from what I'm reading probably sdb), then attempt to mount /dev/sdb to any location. If your card reader is like mine, this mount will fail but you'll find you now magically have /dev/sdb1, /dev/sdb2, etc devices, which will successfully mount... oddness, but it "just works" so I'm happy
    Note that if you plug a card into a slot that is to the kernel, for example, /dev/sda2, then try to mount /dev/sda1, this will (obviously) fail, so be sure to try mounting all the devices that magically appear (if any do).
    -dav7

  • How is the com.sap.runtime.logon.par implemented?

    Hi all
    I want to make some changes to the logon.par file such that if the user authentication fails, I have to fire a custom RFC to check if the user exists in that backend system.
    First of all, I have no clue about how I am going to implement this. Before jumping deep, I'd like to understand how the existing authentication works. Where does the logon get information about the user credentials?
    Any information would be very helpful.
    Thanks
    J

    Hi J,
    The logon process is implemented through two layers, of which the one you have referred to is just representing the user interface, whereas the real logon process is implemented through login modules; for the latter see http://help.sap.com/saphelp_sm32/helpdata/de/46/3ce9402f3f8031e10000000a1550b0/frameset.htm
    On both layers, you can determin if the logon worked or failed (to be concrete, the login module determins this by its own, whereas in the logon PAR you can determin the result of this process). So both layers could be used to implement this. As the login module is more generic, I would advise to use this, as this is also documented and supported, whereas in the login module you would have to modify the implemented logic (by decompiling or putting your logic into some existing JSP). The internal logic of the logon PAR is not documented (but not hard to understand when checking the JSPs and/or decompiling the code).
    Hope it helps
    Detlev

  • Controll flow of logon par files

    Hi ,
    In portal we are using two std par files 1.com.sap.portal.runtime.logon_api. && 2.umelogonbase
    Can any one help ,How exactly the controll flow is happing here , when we type user name & password on logon screen.
    And what is the use of there two par files. What I want to do ,If i need to design an logon page with out these two par files...
    Any ways are there to achive this requirement... Pls help me out....
    Cheers
    Rabin D

    Rabin,
    There are numerous threads already on this topic -
    You need to customize only one file in the customer namespace : com.sap.portal.runtime.logon.par which internally uses umelogonbase.jar and  com.sap.portal.runtime.logon_api.jar.
    Go through the below links for SAP Logon customization - This would make it easy !
    Portal Customizations Intro - Login Part 1 - > Portal Customizations Intro - Login Part 1
    Portal Customizations Intro - Login Part 2 - > Portal Customizations Intro - Login Part 2
    Customizing Portal Logon Screen
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
    A fast and easy Portal logon page customizing
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/371e9d90-0201-0010-c39c-fd2956154ab3
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a000df6b-586a-2910-e6be-9fee831d5a30
    ~ Dhanz

  • Replacing standard  usermanagement par with custom usermanagement par

    Hi all,
    I had to make some changes on the standard user administration(like hiding fields, creating new fields), for which I have downloaded the standard com.sap.portal.usermanagement.admin.par.
    i made a copy(com.***.portal.usermanagement.admin.par) of it and made the changes it works fine with all the changes when I run it from portalapp.xml
    Now I need to put this par file in place of the standard one for the changes to effect.
    Any idea what all configuration changes do I need to make
    thanks in advance
    Paul

    Detlev
    I have made similar changes to the com.sap.portal.runtime.logon par. which is the logon page to the portal.
    What I have done there is made a copy of the standard par, customised it.
    Now I copied the custom par back into the PCD.
    Then I modified the authshemes,xml file, replacing all the occurances of string com.sap.portal.runtime.logon with com.***.portal.runtime.logon(custom par).
    Restarted the j2ee engine , I have the new logon page working.
    I have all the standard functionality working fine along with the changed look and feel.
    I m thinking there should be a similar way out for the usermanagement par too.
    let me know if u have any inf.
    thanks.

  • Need Class file of Reset Password in Logon par??

    Hi,
    I'm working on Forgot Password functionality in Logon par... I want to send customized mail to user once he click on Submit button of the Forgot Password application.
    Can anybody help me to find that..Which class file is being called in Logon par once user enter e-mail id in the text box and click on Submit button..
    I need to change the logic in this class to meet my requirements.
    Thanks a lot!!!
    -Vikas

    hi,
    first step is to select right par file.
    name of par file is :com.sap.portal.support.logon.par
    upload this PAR file to NWDS.
    code for Login page is present in the JSP-umLogonPage.jsp
    path for JSP file is
    dist\PORTAL-INF\umLogonPage.jsp
    regards,
    jayesh talreja

  • Customizing logon problems page

    Hi,
    I'm working on EP 7.0   ,my logon problems page is not enabled  ,plz help me  how to configure it

    HI
    authschemes.xml file change the com.sap.poratl.runtime.logon with your par file name
    This blog explains step by step procedure for Custumzing the Portal Logon Screen
    Modifying The Logon Par(or customising the Logon Screen)
    A fast and easy Portal logon page customizing
    Portal Customizations Intro - Login Part 2
    Portal Customizations Intro - Login Part 1
    http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
    Hope this helps,
    Regards,
    Arun

Maybe you are looking for

  • RFC call in a Webdynpro Java help?

    Hi all, I need used in my webdynpro Java a FM that I created in R3. Exactly I need load in a combo box  the results of my function module. I do it this but not works correctly. I think thats my code is not correctly..Anybody can help me? public void

  • Acrobat Pro XI gives an error when trying to use the Get the Others to Sign feature.

    The error is "There is a system error. Please try again later." I use my Adobe ID for both Acrobat and EchoSign to log in but Acrobat will not connect to EchoSign.  I would like to send documents from Acrobat without having to load them into EchoSign

  • No sound in os 9.2.2

    Hallo everybody, I have exactly the same problem as "elzef" from France, post: Nov 19, 2005, 12:53PM. I have also tried everything I know to find a solution like zapping the pram, nvram, clean installation on another partition, but in vain. I searche

  • Cant get Remote tunnel to establish

    It has been several years since I last setup a site to site tunnel.  Have been trying to set on up today and I must be missing something. Here is the config for the site to site tunnel on the remote ASA - access-list nonat extended permit ip 172.16.1

  • Deserialize Object Invalid Class Exception

    I receive the followign error when attempting to deserialize an Integer class: java.lang.Integer; Local class not compatible: stream classdesc serialVersionUID=1360826667802527544 local class serialVersionUID=1360826667806852920 java.io.InvalidClassE