Skip to Content
0
Nov 28, 2007 at 08:47 AM

Problem with ABAP backend authentication

387 Views

Hi all,

we have a huge issue with the user authentication in our

EP 7 SP12 (J2SDK
1.4.2_13) on SUN Solaris 10 with DB2

installation:

Last week we set the portal authentication to work against an ABAP backend system -

configuration was straight forward, no special settings where applied. First everything

seemed fine, users where able to logon and work with the portal using authentication

against the ABAP backend. Then we discovered that in case a user session timed out,

that user was not able to logon to the portal anymore until we set it's ABAP backend

password to inital!!!

This strange behaviour occurs with ALL our users. They can logon with their username

and password from the ABAP backend and work in the portal; but if their session times

out and they are redirected to the logon page, they cannot logon anymore until we reset

the password in the backend system.

In the portal server log I can see the following errors (actually hundreds of them)

corresponding to problems with user authentication:

An exception was thrown in the UME/ABAP user management connector that

was caused by unavailability of the RFC communication with the backend system:

"Kennwortanmeldung nicht mehr möglich - zuviele Fehlversuche!".[/code]

The next error is always like followws:

Error while populating "USER.R3_DATASOURCE.9910022"

com.sap.security.core.persistence.datasource.PersistenceException:

Kennwortanmeldung nicht mehr möglich - zuviele Fehlversuche!

I read that there is something with the RFC connection, how can I trace that?

Second: Can anyone tell me why the portal is stating that their have been too many

false logon attempts? The users are just redirected to the logon page, try to loggon

once and then they get p*** off and call me 😔

I'd highly appreciate if someone could shed some lioght on this as it is really getting me

into trouble here.

Kind regards,

Christian

Following is a list of the complete errors in the log:

An exception was thrown in the UME/ABAP user management connector. This

exception might be caused by incorrect user input. It is written to the trace to assist

incident analysis by SAP. Only messages also appearing in the log require

administrator assistance.

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:

Kennwortanmeldung nicht mehr möglich - zuviele Fehlversuche!

at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Client640.execute(R3JCo640Proxy.java:465)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserGetDetailInternal(R3Persistence.java:5238)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.doBapiUserGetDetail(R3Persistence.java:6717)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.doDispatchRead(R3Persistence.java:4433)

at com.sap.security.core.persistence.datasource.imp.R3Persistence.populatePrincipalDatabag(R3Persistence.java:917)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.getPrincipalDatabag(PrincipalDatabagFactoryInstance.java:2436)

at com.sap.security.core.imp.User.init(User.java:244)

at com.sap.security.core.imp.AbstractPrincipal.(User.java:203)

at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:364)

at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:288)

at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:308)

at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:387)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1397)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1433)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1448)

at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.getIUserFromPrincipal(SAPJ2EEAuthenticator.java:784)

at com.sap.security.core.logon.imp.SAPJ2EEAuthenticator.getLoggedInUser(SAPJ2EEAuthenticator.java:170)

at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.getLoggedInClientUser(ClientUserFactory.java:218)

at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.getLoggedInClientUser(WDClientUser.java:138)

at com.sap.netweaver.bc.uwl.ui.utils.ServiceManagerHelper.initializeUserContext(ServiceManagerHelper.java:119)

at com.sap.netweaver.bc.uwl.ui.utils.ServiceManagerHelper.getUserContextForMonitoring(ServiceManagerHelper.java:68)

at com.sap.netweaver.bc.uwl.ui.UWLMainView.wdDoModifyView(UWLMainView.java:200)

at com.sap.netweaver.bc.uwl.ui.wdp.InternalUWLMainView.wdDoModifyView(InternalUWLMainView.java:1133)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

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:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

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:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)