SAP SSO Ticket issue after BW(ABAP+JAVA) split

[Former Member]

Dear Experts,

We are performing a BW (ABAP+JAVA) split in sandbox environment.

OS: Aix

DB: Oracle

NW:7.01

I took a java export and installed in new server and performed the post steps in RSPOR_SETUP. Changed the system object in system landscape of portal. I have selected the option of send assertion ticket in the RFC. Exchanged the certificates between ABAP+JAVA as well. However when i invoke any web reports throws an error as below.

Issuer of SSO ticket is not authorized

When i checked the work process trace able to find the error as below.

N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1065]

N  {root-id=5576E25FE25E00A0E10000000A440017}_{conn-id=00000000000000000000000000000000}_0

N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1071]

N  {root-id=5576E25FE25E00A0E10000000A440017}_{conn-id=00000000000000000000000000000000}_0

N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1065]

N  {root-id=5576E25FE25E00A0E10000000A440017}_{conn-id=00000000000000000000000000000000}_0

N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1071]

But the table entry has the below values

400   <ABAP SID>     400

400   <JAVA SID>      000

Is there any other steps need to be carried out. Please update.

[Former Member · Accepted solution]

Hi Raja,

Check that you have maintained the correct system name and client number in ACL.
Default JAVA client is 000

Regards,

Vikas Sharma

[Former Member · Accepted solution]

Hi Vikas/Sriram,

Let me check the note and come back to you.

Yes client numbe rin ACL is 000 for JAVA. Mentioned the same in my message itself.

Is it anything to do with JAVA Certificate and security provider of the JAVA stack?

CN=<SID>,OU=J2EE is the current issuer of the java ticket.

Regards,

Raja. G

[Former Member · Accepted solution]

Dear All,

Thanks for your help.

We resolved the issue. Please find the solution below.

• During the BW(ABAP+JAVA) dual stack the login.ticket_client parameter points to the PRD client of ABAP. However after the split need to change it back to default.
• The ticket ID mentioned in the evaluteticketassertion need to changed accordingly if we generate the certificates.

Regards,

Raja. G

[divyanshu_srivastava3]

Hi Raja,

N  *** ERROR => System ID and client from ticket are not the same than mine. [ssoxxkrn.c   1065]
N  {root-id=5576E25FE25E00A0E10000000A440017}_{conn-id=00000000000000000000000000000000}_0
N  *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL (see note 1055856). [ssoxxkrn.c   1071]

If you see the trace above, it point to a KBA - 1055856 - which talks about certain points which you should cross verify.

Additionally, refer

1769367 and 1903560

Regards,

[Former Member]

Hi Divyanshu/Sriram,

I have already went across the notes mentioned. Everything is fine.

We are using the ABAP UME only.

Kernel is 721 patch 400.

Regards,

Raja. G

[Sriram2009]

Hi Raja

Thanks for your information.

Using this tool could check the BI ABAP to JAVA connectivity

937697 - Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool

BR

SS

[Sriram2009]

Greeting to Raja

1. Have you check the SAP Note 1055856 for this issue?

2. Kernel version & release?

BR

SS