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" ?>
- 
- 
- <document>
- <authschemes>
- 
- <authscheme name="uidpwdlogon">
- 
<authentication-template>ticket</authentication-template>
<priority>20</priority>
- 
<frontendtype>2</frontendtype>
- 
<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>
- 
- <authscheme name="anonymous">
<priority>-1</priority>
</authscheme>
</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

Similar Messages

Customizing Logon Page CE 7.1

Hi everyone,
It is possible change the Logon Page in CE 7.1?
Someone has the steps to do this?
Regards,
Eduardo Campos.

Check the below help links for customizing the logon page in CE 7.1
http://help.sap.com/saphelp_nwce10/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_nwce711/helpdata/EN/48/ee941b0b803697e10000000a42189b/frameset.htm
Also the thread
how to change the login screen
Raghu

Customizing logon page in EP 7.0

hi,
may i know how to change logon page branding image,Welcome test in logon page?i'm not aware of EP7.0.Rpl ASAP.
thks
Kiran

Hi Kiran,
Check this link
Portal Branding for specific user
Portal Customizations Intro - Login Part 1
Portal Customizations Intro - Login Part 2
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N08_BB_ConfigGuide_EN_US.doc
Is your Portal Logon Page more colorful?
Portal themes
Regards
Arun

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

Portal runtime error, custom logon page HElpp

Hi,
I'm new to EP, please kindly help me to solve my problem
I've read so many topic about this, but I still can't understand what I'm supposed to do.
I want to change umHelpPage, so I download by using system administration -> support -> support desk -> portal runtime -> browse deployment -> root -> web-inf -> portal ->portalapps -> com.sap.runtime.logon
Then, download and I make certain changes in UmHelpPage, directly in winzip,without extract it. Save, and then change .zip to .par, by using system administration -> support -> support desk -> portal runtime -> administratioin console -> upload -> com.sap.runtime.logon.par
At first, after I upload the com.sap.runtime.logon, all of my jsp files are missing. And then I'm facing the following 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
Previously, I have backed up my com.sap.runtime.login.par in my local. After several times trying to upload , my jsp files still missing. Then, I tried to copied them manually one by one, from my original backup to folder /irj/root/web-inf/portal/portalapps using unix. But, the error still exists.
I also download .bak one in the pcd directory and renamed in .par and upload it again, but it doesn't make any changes.
I've also checked the .jar files. In my lib folder I have 2 files :
- com.sap.runtime.logon.logon_api.jar
- umelogonbase.jar
but i don't have the com.sap.runtime.logon.logon_core.jar one. Is the file also important ? if so, in which directory I can have it?
Please tell me, what I have to do ?
I have original back up in my local, and seems like I accidentaly erase the original one in the portal.

Hi Desiana,
I think you are missing something in your portalapp.xml
See the sample..
<components>
 <component name="DeploymentChecker">
 <component-config>
 <property name="ClassName" value="com.shell.ep.sapportals.epone.adminviews.page.DeploymentChecker"/>
 </component-config>
 <component-profile>
 <property name="tagLib.inheritance" value="final"/>
 <property name="tagLib.value" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-profile>
 </component>
</components>
Regards,
[email protected]

After upgrade to 4.1 from 3.2, admin logon page error with "done error load

Hello all,
Just upgraded 3.2 to 4.1. ran @apexins.sql sysaux sysaux temp /i/. Installation was successful and upgrade completed with no errors. When trying to log on to admin page, url changes to admin workarea but with IE we get "done error loading pages" and logon screen doesn't appear. All objects are compiled, accounts are unlocked and valid. Same thing happens when attempting to logon to the applicaiton. Any help would be appreciated. Open SR with oracle support, but no reply since yesterday.
inital url: https://xxxxxxxx.xxx.com:8443/pls/apex/apex_admin
ending url: https://xxxxxxxx.xxx.com:8443/pls/apex/f?p=4550:10:903647939084101
"done error loading pages"
Edited by: user12128153 on May 18, 2012 2:21 AM

Hi user12128153 (a real name would be nice),
a few questions for you.
Do you experience the same errors with firefox? If so install firebug (if you don't have it already) and see if the errors have to do with missing css etc.
What application server do you use, OHS/Apex Listener etc?
Kofi

Custom Login page error

HI,
I am trying to modify the Apps login page. I just renamed the page AppsLocalLogin.jsp to xxxAppsLocalLogin.jsp and try to access from the server. This gives me error
java.lang.RuntimeException: Cannot access oracle.app.fnd.sso
Here .app. access though in oracle apps folder structure there is not folder like app
Can anybody help me on this why this error is coming.

Security layer may display error messages which has no meaning and not helpful to to figure out what is the root cause. You can addres this to the Security forum if you hit there. But have the same question Ram asked. Any need to change the jsp name?

Logon Page Customization in SAP Portal 7.31

Hi Experts,
I am planning to change the look and feel of the Logon Page for Portal.
The current page is already a customized one.
For making the changes, I requested and got the following files.
1. tc~sec~ume~logon~ui.war from <drive>:\\usr\\sap\\<SID>\\J00\\j2ee\\cluster\\apps\\sap.com\\com.sap.security.core.logon\\servlet_jsp\\logon_ui_resources\\tc~sec~ume~logon~ui.war
and
2. tc~sec~ume~logon~logic_api.jar from drive>:\usr\sap\<SID>\J00\j2ee\cluster\apps\sap.com\com.sap.security.core.logon\servlet_jsp\logon_app\root\WEB-INF\lib
The below is the screen shot of nwa/auth properties.
The file which was sent to me and the properties look like, standard logon module only.
I am not sure if the file is the custom one. How to find if its customized. In the layout folder, I couldn't fine any images in the current custom logon page.
I don't have access for deploying the ear. I have to send to the Server team and they only will be able to deploy.
Kindly advise me on how to proceed with.
Kind Regards,
Jelbin

here is the standard link for logon page customization for NW7.31 check it:
Developing a Custom Logon Screen - Developing Authentication Enhancements on the AS Java - SAP Library
if your are modifying a existing custom logon page first you will be requring the source code of that custom logon page ,Get it and import it in NWDS and follow the steps mentioned in standard help.
if source code is not available ask your server team to provide the custom logon page EAR file ,reverse engineer it by importing the EAR in NWDS and modify it as per your requirement and following the steps mentioned in help.
to know if you are modifying the correct EAR go to application.xml and check what is the application alias mentioned over there same will be configured in NWA under alias for application for login
as per your screenshot its mentioned as /new_logon
<context-root>new_logon</context-root>
Also check the J2EE engine .xml and check if you have your client name mentioned as company name.
Other check you can do id check images in the war file if those are present which are appearing on logon page when open,you can right click on image on opened portal logon page and get its name check in NWDS imported project war file if those images are present.you can do other chaecks in rendered code as per your customization to confirm if you are modiftyinfg the correct logon page ear or war file.
i guess if you dont have any the previous custom ear it might be under your provider location and application alias folder location not sure of it though :
<Installation drive>:\usr\sap\<SID>\J00\j2ee\cluster\apps\<providername>\com.sap.security.core.logon
\servlet_jsp\new_logon\tc~sec~ume~logon~ui.war
you can ask your server team if they found any war file in folder <provider name> or application alias folder or how many war file they found if they search with tc~sec~ume~logon~ui.war file ,aks them to give the one which is situated in your <client/provider.com > folder.
hope this helps.

Portal Logoff and redirect to my own (created) logon page

Hi experts,
one Question about "Portal logoff and redirect to another URL", and I know there already are solutions how to fix that, but I was not successfull with my doings.
I have a customized logon page. When I call "http://myportal:50000/irj/portal/anonymous", I can see my own logon page. That works fine.
Now to my problem:
1) I'm using SAP NetWeaver Portal v7.01 (VMWare) with Windows 7 (x64 Bit)
2) In Config Tool "ume.logoff.redirect.silent" is setted at true and "ume.logoff.redirect.url" (both under "Global settings") at "http://myportal:50000/irj/portal/anonymous". Than WebAS has been restarted.
3) In source code of the Portal page (Masthead), I could see that the setted values can be readed from config tool
4) So far I could understand, when the parameters are setted and "silent" is true, than a new iframe will be created which is append to the document (JavaScript: logoffThirdParty())
5) After this, the logoff form will submitted, that means xxxx.LogOutComponent is running. Think this components reads some hidden attributes as "logon_submit", and one of this should be the (new created) externalIFrame
Instead of my anonymous page, I see the default SAP logon page. I don't have made any changes on com.sap.portal.navigation.masthead iView (should be the right name I think).
Thanks for assitance and regards,
Cengiz
Edited by: Cengiz Türkoglu on Feb 5, 2010 8:39 PM
Edited by: Cengiz Türkoglu on Feb 5, 2010 8:39 PM

Try to set the value ume.logoff.redirect.silent to FALSE and then restart and test. In my situation it worked.
Regards,
A

Custimized logon page doesn't work after upgrade

Hi experts,
We have custimized the portal logon page, and during an upgrade it is no longer working. It is back to the standard logon page.
We have created our own .par file and deplyoed it (it is still there after the upgrade) and in the "direct editing" tab in the portal we can still see that the login.authschemes.definition.file is pointing towards our own developed .xml file.
Our customized page has worked fine for a long time, so I am puzzled why it does'nt work after the upgrade. If we had changed any standard SAP, I would understand that things would be overwritten, but we haven't...
It may be worth mentioning that the uploader .par file was marked as 'not installed' after the upgrade. I just clicked 'install'...
Does anyone have any idea of what we should do?
1: Get the customized logon page working again and
2: How to prevent this from happening again?
Regards,
Stina.

Anyone else with any good ideas?
Our custom authschemes.xml file has been validated, and the .par file has, as previous mentioned, been deployed.
Does anyone know of any way to confirm that the .par file is being used by the .xml file? Could this be the breaking point? Anyone with any good ideas on how to verify that?
All help is highly appreciated, and rewarded:)
Regards,
Stina.

Problem - Logging to portal with Custom Logon iview

Dear Experts,
I have created a custom Logon page(Iview out of PAR) with simple JSP with fileds user id as j_user and password j_password. In the action of the form i submit it to "/irj/portal". When the user id&password is correct it loggs in to the portal Correctly. but when the password is wrong it goes to the default Logon screen with the message 'user authentication failed'. Now i want to handle this in my custom logon page itself and donot want to show to the default page.
Now i need to validate the user id and password before submitting the form. how can i do this, has some one done this before. Can u please send me the sample project to [email protected]
Its Urgenty and Points will be awarded.
Thanks
Md. Yusuf

Hi All,
The problem was solved using PortalComponent using JSPDynpage, where i do the validate the user in a bean through the code.
     public boolean checkuserid456 ( String sh1, String sh2 ) throws UMException
          boolean bolval=false;
          try {
          String ssh1 = sh1;
          String ssh2 = sh2;
          IUserAccount ua = UMFactory.getUserAccountFactory().getUserAccountByLogonId(j_user);
          final boolean passwordCorrect = ua.checkPassword(j_password);
          bolval = passwordCorrect;
          catch(Exception e){
If the value returened is true from the dynpage i direct it to success JSP else i go back to the same first JSP page.
Thanks
Yusuf

Error on Portal Logon Page

Hi Experts,
We are getting exception while calling the Portal URL.
Recently, we changed the password policy and made some customizations on the com.sap.portal.runtime.logon.par file.
After that when I tried to access the Logon page, it gave an exception.
I even replaced the customized logon par file with the original one but it did not help.
Please note that I deployed the logon par file with the same name, so I did not have to make any changes in the authschemes.xml file.
So ideally when I replaced the customized PAR file with the original one, it should have worked out.
Can it be because of some UME property "Password Policy change" or something like that which has been changed by our Basis team in the Config tool and which is creating issues now.
Is there any connection between the UME property and the Portal Logon page? I know that UME comes into picture once the user clicks on Login button after entering the login credentials but does it also come in picture at the portal logon page call?
We are not able to trace out the root cause as both Password Policy Change and deployment of PAR was done parallely due to which we are confused about the cause of the issue.
Please find below the trace against the exception ID:
#1.5 #5CF3FC5B7E1C00670000000300001B400004ACA7F25E4315#1315737232519#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##8b1ef68fdc6111e0a5840000061bff66#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###04:03_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C00660000000100001B400004ACA7F2896FC1#1315737235348#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###Shutting down Application Brokerage...#
#1.5 #5CF3FC5B7E1C00660000000800001B400004ACA7F2940472#1315737236039#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Java###[PortalServiceItem.release] exception caught releasing com.sap.netweaver.coll.appl.rtc|RTCClientPollingService
[EXCEPTION]
#1#java.lang.NullPointerException
 at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.unsubscribe(RTMFMessaging.java:1040)
 at com.sap.ip.collaboration.core.api.rtmf.core.cluster.ClusterSystemManager.unsubscribe(ClusterSystemManager.java:133)
 at com.sap.ip.collaboration.core.api.semantic.services.RTCBaseService.destroy(RTCBaseService.java:146)
 at com.sapportals.portal.prt.core.broker.PortalServiceItem.release(PortalServiceItem.java:389)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1159)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
 at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:575)
 at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:680)
 at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)
 at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:731)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)
 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:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #5CF3FC5B7E1C006F00000002000016140004ACA819F31491#1315737896495#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##1647a148dc6311e0aaaa0000061bff66#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Java###04:14_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
#1.5 #5CF3FC5B7E1C007000000000000016140004ACA81A149C1D#1315737898689#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0##n/a##18319b2cdc6311e092af0000061bff66#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server#Java###An error occured during authscheme computation.
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.runtime.logon.certlogon
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
 at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:233)
 at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:177)
 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:275)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sap.portal.navigation.Gateway.service(Gateway.java:117)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 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:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component com.sap.portal.runtime.logon.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)
 ... 33 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)
 ... 37 more
Thanks & Regards.
Anurag

Hi,
Check if your portalapp.xml has an entry "<property name="ClassName" value="com.sapportals.portal.ume.component.logon.SAPMLogonComponent"/>"
If it is there, then I feel that this is an issue with jar files not getting imported properly.
Just try including these two jars (umlogonbase.jar and com.sap.portal.runtime.logon_api.jar) from
usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.logon\lib
and copy manually to the lib folder under PORTAL-INF in your project.
Regards,
Vijay.

Portal Runtime Error: Logon Page Modified!!!!

Hi all
I have modified the Logon Page to include a New Drop down.
I copied com.sap.portal.runtime.logon.par.bak to my NewParProject0.par and modified the Logon Page with the Following code addition:
 <tr>
 <td width="161" height="20">
 <label class=urLblStd for="logonCltfield">
 <%=logonLocale.get("CLIENT")%>
 *
 </label>
 </td>
 <td>
 <select id="clientType" class="DROPDOWN" style="width:2in">
 <option CLASS="DROPDOWN" value ="100" selected>100</option>
 <option CLASS="DROPDOWN" value ="110">110</option>
 <option CLASS="DROPDOWN" value ="120">120</option>
 <option CLASS="DROPDOWN" value ="130">130</option>
 </select>
 </td>
 </tr>
The above process is done as per the documentation given in the Customizing the Logon Screens
After building the new par file, I moved it into the ...\deployment\pcd
And i modified the authschemes.xml as per the details given in the help.sap.com(Changing the authschemes.xml File)
And even i tried changing value of the property login.authschemes.definition.file to the name of the new authschemes file.
I facing the following 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..
Help please!!!!!!
Thanks
Kam

Peter
My Logon screen will get 3 credentials from the User .
 1. User Id (Text appearing in the Screen is User)
 2. Password (Text appearing in the Screen is Password)
 3. Client (Text "CLIENT" should appear similar to the User Id and Password).
The Value field for the CLIENT should be of type DropDown.
Hope my requirement is clear. Please Advice on the procedure to be followed...
Thanks
Kam

Logon page modication preview works but errors when assigned to Authscheme or as appication alias or both

Hello Experts,
Our portal is being upgraded from 7.01 to 7.31 SPS 10, we have a customized logon module and are trying to migrate this application. As part of migration, we followed below steps -
1. Convert the par to ear using Par conversion Tool
2. Import into Java EE perspective of NWDS 7.31
3. Migrated the project to Java EE
4. Corrected jar class library from 7.31 except com.sap.security.core.imp.TenantFactory, which is not available in 7.01 or 7.31
5. Updated application.xml and application-j2ee-engine.xml as suggested in site with context_root and dependency on om.sap.portal.runtime.login6. Tried to deploy to server, the ear file got deployed
7. Previewed and the application was showing coming well with customizations
8. Logged into nwa/auth and edited ume.logon.application.ui_resources_alias to point to alias defined in the application.xml
9. Result:all logon related screens were coming as blank, logon was not possible from any of the links - irj/portal, nwa etc
10. Tried restarting, modifying authschemes along with editing the ume property. All combinations were tried but no luck.
I have done some investigation on internet, and have seen replies that all the JSP errors need to be resolved to get through the blank logon pages, but I still have 340 erorrs and out of which 320 are JSP erros on variables from <include> text files, more or less NWDS errors. and remaining 20 are related to com.sap.security.core.imp.TenantFactory. There seems to be no scope to clear these errors as these seems to be eclipse compilation realted or getting an library file which is not existing in 7.01 or 7.31.
Any inputs from your side on this situation on in general migration of logon pages to 7.3X would be helpful?
Official references referred so far:
1935486 - NetWeaver Portal 7.3X/7.4 and custom logon screens
1938160 - Portal irj throwing runtime exception after upgrade when using custom logon component
http://help.sap.com/saphelp_nw73/helpdata/en/23/c0e240beb0702ae10000000a155106/content.htm
http://help.sap.com/saphelp_nw73/helpdata/en/7b/4928ad21714996ad5cb987cdd81b33/content.htm
http://help.sap.com/saphelp_nw73/helpdata/en/1a/3afd4e641b8f42ac07bb77fe30375b/frameset.htm
Thanks,
Vamshi

Hi vamshi,
Can you please paste the error?
Regards,
Nitin

Sharepoint 2013 - Error while applying custom master page.

I am getting following error on my sharepoint 2013 site on applying a custom master page.
System.ArgumentNullException: Value cannot be null. Parameter name: ribbon at Microsoft.SharePoint.WebControls.RibbonTrimmer..ctor(SPRibbon ribbon) at Microsoft.SharePoint.WebControls.SPPageStateControl.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at Microsoft.SharePoint.WebPartPages.WikiEditPage.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Does anyone know whats wrong with my custom master page?

Hi,
please check if its properly deployed.
Refer the similar thread below.
http://social.technet.microsoft.com/Forums/en-US/f07ce2f6-6607-4764-8c12-10de4ae1d635/systemargumentnullexception-value-cannot-be-null-parameter-name-ribbon?forum=sharepointgeneralprevious
Please remember to click 'Mark as Answer' on the answer if it helps you

Custom Logon Page Error

Similar Messages

Maybe you are looking for