Skip to Content
author's profile photo Former Member
Former Member

Assertion ticket blues in RFC between ABAP and J2EE

I am integrating BI Java on one system with BI on another system.

There is a JCO RFC provider on the J2EE side and a corresponding RFC on the ABAP side.

But...when I test the RFC connection from ABAP it fails. In the trace of the workprocess I see this:

N create_AuthenticationAssertionTicket was called.

N *** ERROR => Sign failed with rc = 5. [ssoxxsgn.c 327]

N *** ERROR => uResult=22. [ssoxxsgn.c 330]

N Unknown signer. Security profile does not contain the correct private key.

N *** ERROR => DefaultSign failed with rc=1441801. [ssoxxsgn.c 373]

N *** ERROR => Ticket creation failed with rc = 1441801. [ssoxxkrn.c 493]

N *** ERROR => dy_signi_ext: ticket creation failed [sign.c 10651]


In the RFC trace I can see this:

RFC> AssertionTicket create failure

The connection was automatically created executing the BI Java template.

Any suggestions on what is wrong here?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Mar 06, 2007 at 12:34 PM

    Creating a new PSE solved the problem....

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.