cancel
Showing results for 
Search instead for 
Did you mean: 

BI Java Login Issue Using ABAP Backend following SPS 20 Patch level 1

Former Member
0 Kudos

Dear Gurus,

Following the patching of our BI Java Stack to SPS 20 we were unable to run the template installer it would fail during the creation of the SAP_BW system. During the period of time where were at the SPS 20 level and logins to the BI Java stack were successful. However, after applying SAP #1385108 and patching using the components listed in note 1385108 to patch level 1 logins no longer functioned properly. The componenet updated was EP-PSERV and the two CA's applied were:

EPBC220P_1-10003489.SCA Patch for PORTAL FRAMEWORK 7.00 SP20

EPPSERV20P_1-10003474.SCA Patch for PORTAL 7.00 SP20

After the note was applied logins no longer functioned as expected. Users authenticating with the proper ID and password continually receive a login screen even though the server0 security log indicates a successful login. When an incorrect user name or password is sent to the BI Java stack it is able to differentiate that the authentication for the user is incorrect and server0 security log confirms the result.

I have validated that the SAPJSF user is unlocked and is assigned the SAP_BC_JSF_COMMUNICATION role.

With that being said it appears that there is not an issue with communication b/w the BI Java Stack and ABAP backend.

Please advise,

John Kiser

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Below is an except from the server0 security log following a successful login attempt and unsuccessful. However, in both cases the login page is just redisplayed. The difference is after a successful login attempt a fresh login page appears as if nothing has happened, but after an unsuccessful attempt a red asterisk appears and indicates a login failure.

Successful:

#1.#00144F3AFD1E006E00000006000057AD00047998AAB63264#1259596512899#/System/Security/Audit#sap.com/com.sap.security.core.admin#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#299##iempmsfc71_JN1_4800250#J2EE_ADMIN#be98480cddc811dec5bd00144f3afd1e#SAPEngine_Application_Thread impl:3_28##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN | LOGIN.OK | USER.R3_DATASOURCE.J2EE_ADMIN | IP Address=xxx.xxx.xxx.xxx#

Unsuccessful:

0144F3AFD1E006F00000001000057AD00047998B46E8C36#1259596675976#/System/Security/Audit#sap.com/com.sap.security.core.admin#com.sap.security.core.util.SecurityAudit#J2EE_GUEST#0##iempmsfc71_JN1_4800250#Guest#1fcdb399ddc911dececd00144f3afd1e#SAPEngine_Application_Threadimpl:3_38##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_GUEST| LOGIN.ERROR | null | | Login Method=\default, UserID=J2EE_ADMIN, IP Address=xxx.xxx.xxx.xxx, Reason=Authentication did not succeed.#