Modification of Logon Par

Hi Guys,
Does anyone of you encountered the error below after modifying the logon par? I already have changed authschemes.xml to point to the new component but still encountering the issue. please help.
com/sap/engine/applications/security/logon/LogonApplicationPermission.
Exception id: 03:14_03/03/09_0001_2206150
See the details for the exception ID in the log file
Thanks,
Robert

hi
check this this may be the one of the reason
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/297f35cf-0201-0010-00b2-fe2f3e23d360
https://ww2.avispublicsduparisien.com/irj/portalapps/com.sap.portal.pdk.srv.usermanagementengine40/docs/overview.html
bvr

Similar Messages

Modifications in Logon par

Hi,
I would like to modify the performpassword check method in SAPLOGONLOGIC class file in Logon par file.
How can I modify the class file. Please help me on this.
Ram

Hi,
You can use Java Decompiler for extracting contents of your class file
Refer this link:
ftp://ftp.sac.sk/pub/sac/utilprog/djdec377.zip
If the above URL does not work check here:
http://dj-java-decompiler.en.softonic.com/download
Edit the contents and recreate the class file again.
This will help you solving problem.
Regards
Kedar Kulkarni
Reward points if useful
Edited by: Kedar Kulkarni on Jun 13, 2008 12:40 PM

Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

Hello,
We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
This is what we've done:
We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
Please, do you know what could be the problem?
Thanks in advance

Hi Belen,
Here are the steps you would need to take
1. import the original par file into the NWDS and name the project as
    com.sap.portal.runtime.logon
2. Make sure the project name is com.sap.portal.runtime.logon
3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
    a local directory
4.Under the lib you would find two jar files copy them and paste them in your project
   under dist>PORTAL-INF>lib directory
5.move the files cert....till umResetPass....jsp into the PORTAL-INF directory
6. export the par to the server in question
7. restart your server
This should solve your problem..
Thanks,
Gokul

Error while importing logon par file

Hi
I have to do logon page customisation for that i have taken com.sap.portal.runtime.logon.par.bak file from basis team and i saved it to my desktop .Now i have renamed it to com.sap.portal.runtime.logon.par and trying to import to my NWDS.
So i opend EP perspective file->import->browsed the par file in place of Archive file name when i click on finish it is showing the error "invalid END header(bad central directory offset).
"The plugin com.sap.portal.plugins.config-archiver"caused an exception during the unpack operation.see log for more details"
Can anybody please let me know the reason for this error .
Thanks in advance.

Hi,
After renaming com.sap.portal.runtime.logon.par.bak to com.sap.portal.runtime.logon.par. Try opening the file with winrar/winzip to see if you have a right par file structure. On some portal versions, when you open com.sap.portal.runtime.logon.par file, you have again a com.sap.portal.runtime.logon.par file inside it.
So if you find com.sap.portal.runtime.logon.par file inside com.sap.portal.runtime.logon.par. Then just extract it again and try importing it into NWDS.
Please refer to [link|NWDS Log - PAR import error;
Hope this helps!!
Thanks & Regards
Vijay

Error while importing logon par file into NWDS.

Dear Friends ,
I m trying to customise the logon screen for my project. For this I have downloaded the "com.sap.portal.runtime.logon.par.bak" from portal server instance with the help of basis team. I have locally saved this file on my desktop[. I have renamed the file as .par and removed the .bak extension. Now I have tried to import the file onto NWDS in EP perspective by following File>Import>Par file. But its giving me this error:
error in opening zip file
Reason: Sorry, an error occured creating the new project.
The plugin "com.sap.portal.plugins.config-archiver caused an exception during the
"Unpack" Operation See log for more details.
In some of the solutions provided in SDN saying that after renaming the file to par open with zip if i done it is again showing the error as "Start of the central directory not found .Zip file corrupt.Possible cause :file transfer error."
Kindly suggest me the solution.
Thanks and regards.

Hi,
I think you have taken this file from a wrong path and hence this issue.
Pls download the par file from the below path and try importing it into EP perspective..
System admin> Support>Portal Runtime > Browse Deployment>
Browse through the following to find the com.sap.portal.runtime.logon.par.bak file:
WEB-INF u2013> deployment u2013> pcd
Root>WEB-INF>Portal>Portalapps> temp--> download the com.sap.portal.runtime.logon.par.bak
Regards,
Vijay.
Edited by: VijayKPappala on Sep 7, 2011 8:46 AM

Error while deplye logon par file in NWDS

Hello Everybody,
Here I am using EP 7 and SP 14. I have to change my Portal Logon PAR file as I have to add some hyperlinks in my par file.
Now problem is , after importing par file in NWDS i made some changes.Then at the time of exporting file, it ask for deployement. When i deploye par file it is throwing error:
Operation Faliled:please make sure server is running or check log for more details.
so i checked the logs. It is like :
java.io.IOException: Server returned HTTP response code: 500 for URL: http://epdev:50000/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.system.console.ArchiveUploader?login_submit=on&j_user=&j_password=null&j_authscheme=default&uidPasswordLogon=Log%20on
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
     at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
     at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
     at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
     at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
     at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
     at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
     at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
     at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
     at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
     at org.eclipse.jface.window.Window.open(Window.java:563)
     at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
     at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
     at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
     at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
     at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
     at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
     at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
     at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
     at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
     at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
     at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
     at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
     at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
     at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
     at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Kindly help me out. i'll be really very thankfull.
Thanks & Regards
Nivedita

Hi Nivedita,
You could try to delete the entry from the NWDS preferences and set the data there again. Set all the needed information like the portal host name, port, user name. And try not to select the option to save the passwords and check if NWDS does ask for a password then. (Also restart NWDS, I learnt that restart sometimes works wonders :P )
If it yet doesnt work, build the par file and then logon to the portal as administrator and go to tab System Administration->Support->Portal Runtime->Administration Console. Browse to your par file and click on upload.
Good Luck!
GLM

Error deploying logon.par

Hi Experts,
I am trying to change the portal logon screen. I followed the insstructions in the documentation to modify the com.sap.portal.runtime.logon.par.bak
I exported an par file from nwds and copied to the apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd and apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp directory
Also i modified the authschemes.xml and set the corrext value in com.sap.security.core.ume.service via configtool.
The problem is when i restart the server the created .par file changes to .p.err and the following error log is created:
2007-05-16_14-54-15
Application upload failed: com.sap.test.logon.par
com.sapportals.portal.prt.runtime.PortalException: [ApplicationRepositoryService.putArchive] archive: com.sap.test.logon.par
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:328)
 at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(DeploymentManager.java:813)
 at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchives(DeploymentManager.java:599)
 at com.sapportals.portal.prt.deployment.DeploymentManager.populateRuntimeRepository(DeploymentManager.java:582)
 at com.sapportals.portal.prt.deployment.DeploymentManager.runtimeRepositoryDeployment(DeploymentManager.java:310)
 at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:404)
 at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
 at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
 at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
 at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.pcd.pl.PlRuntimeException: unexpected SQLException when calling OpenSQLServices.isTransientSQLError()
Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
 at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:281)
 at com.sapportals.portal.pcd.pl.PlFactory.checkDeadlockResolution(PlFactory.java:2433)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1158)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1100)
 at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:856)
 at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:190)
 at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:190)
 at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:253)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:145)
 at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440)
 at com.sapportals.portal.pcd.gl.PcdGlContext.bind(PcdGlContext.java:369)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.bind(PcdProxyContext.java:469)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebindInt(PcdProxyContext.java:489)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:508)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:494)
 at com.sapportals.portal.pcd.gl.PcdGlContext.rebind(PcdGlContext.java:1254)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:549)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:736)
 at com.sapportals.portal.pcd.gl.PcdProxyContext.rebind(PcdProxyContext.java:741)
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.storeArchive(ApplicationRepositoryService.java:373)
 at com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService.putArchive(ApplicationRepositoryService.java:299)
 ... 20 more
Caused by: com.sap.sql.log.OpenSQLException: Invalid connection type com.sap.engine.services.dbpool.cci.ConnectionHandle.
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
 at com.sap.sql.services.OpenSQLServices.isTransientSQLError(OpenSQLServices.java:742)
 at com.sapportals.portal.pcd.pl.BasicObjectsTable.isTransientSQLError(BasicObjectsTable.java:277)
 ... 40 more
looks like a problem with openSQL. In fact I have defined an additional vendor data source in visual admin that works properly with my application. Is my problem related to that?
Thanks in advance

Hi,
 Before cheking the entire steps at one shot, try step by step procedure.
First just edit the changes and try to deploy and run the new par from portalapp.xml. If the output is correct, then go ahead changing the actual logon page with your new page. Else it will be difficult to find the exact problem. Also make sure the logon par which u have taken for modiifcation comes from the server u r deploying and u use NWDS of same patch. Otherwise there can be mismatches.
Regards,
Vijai

Error in the Portal Logon par

Hi All
i got the error in the logon par customization i have the followed the steps based on the weblog from the following link
Modifying The Logon Par(or customising the Logon Screen)
after done everything i restarted the portal then i got the following error
 Servlet [prt] will be unavailable for undefined time.
Details: javax.servlet.UnavailableException: Initialization of Dispatcher failed
Exception id: [001731424EAC006700000029000013100004346F05987ABE]

please help me on this as early as posible
Regards
Sunil

Hi Sunil,
First of all, put back the original par file and restart the portal. If you have the same problem, it has nothing to do with your changes (unless you changed the authschemes.xml as well).
Download the standard logon par file and compare the structure with your par file. Find the problem (create an iview where you can test your component). If it works, you can try again.
cheers,
Noë

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). Dont 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.

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.
from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().
I am calling a Deployable Proxy in that method by using the below code,
Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);
I am getting the Exception,
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.
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.
from the ResetPassword.jsp , SAPMLogonLogic.java is getting called ,and there is a method called performResetPassword().
I am calling a Deployable Proxy in that method by using the below code,
Gateway objGateway=(SMSGateway)ctx.lookup("java:comp/env/MailProxy");
MailGatewayViDocument objSMSGatewayViDocument=(MailGatewayViDocument )objGateway.getLogicalPort("wsPort_Document",MailGatewayViDocument.class);
objMailGatewayViDocument.sendMail(...);
I am getting the Exception,
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.
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,
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

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 <frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>, <frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget> and <frontendtarget>com.sap.portal.runtime.logon.header</frontendtarget>
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). Dont 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

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

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

Logon Par - redirect to new JSP

Hi,
I've to change the portal logon page.
My requirement is to redirect the logon page to test.jsp page.
from umLogonPage.jsp i'm trying to redirect to test.jsp in form method.
<FORM name="logonForm" method="post" action=test.jsp>
but the URL is not proper.
How can i pass the absolute URL for this.
Thanks and Regards
Puneet

Puneeth,
Its possible to redirect to a JSP page from portal logon Screen.
There are several ways of doing this:-
1. Create a separate portal component (JSP Dynpage) and set the authscheme property is anonymous (because you are calling a portal component from outside) ie.
<property name="AuthScheme" value="anonymous" />
You can follow this method If JSP componentu2019s functionality is Independent than any login functionality.
2. You can modify the SAPMLogonLogic.java file which contains flow logic of all jsp files. The SAPMLogonLogic file is present umelogonbase.jar.
The umelogonbase.jar is under lib folder of the logon par file. Just extract the logon par file and navigate to PORTAL-INF -> lib to get the umelogonbase.jar
Ram

Modification of Logon Par

Similar Messages

Maybe you are looking for