cancel
Showing results for 
Search instead for 
Did you mean: 

Jco Connection test fail : Issuer of SSO ticket is not Authorized.

sowmya_m3
Explorer
0 Kudos

Dear Experts,

While testing the JCO connections for Model data connections am getting


Error : com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized.

I have done the SSO configuration. I have followed all the steps suggested in others threads in scn but still am not able to solve this issue.

Please help me on this.

Regards

Sowmya

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member183915
Active Contributor
0 Kudos

HI,

Check note  1769367 - Issuer of SSO ticket is not authorized .

This might help.

Regards,

Navya

sowmya_m3
Explorer
0 Kudos

Hi Navya,

I have followed the steps in the mentioned note. Still am facing same issue.

Regards

Sowmya

vijay_kumar49
Active Contributor
0 Kudos

Please check your entries in transaction STRUSTSS02.

You must have your client in the ACL.

After that, check the SAP Logon Ticket for your system through Environment -> SAP Logon Ticket.

In the output, you can have a red alert concerning the certificate. Use the Activate button...

sowmya_m3
Explorer
0 Kudos

Hi Vijay,

Am bit confused here, am doing SSO for the first time.

In transaction STRUSTSS02, i have below Certificate Lists.


CN=NSP,

OU=J2EE,CN=NPQ

OU=J2EE,CN=NSP

CN=QLT,C=IN

All there 4 were available befor i do SSO. I have downloaded the SSO cetificate form Portal and removed the 4th entry and added again to certificate list and ACL as well.

But in ACL table now available Entries are as below.

Am doing This in client 555 and System Id :NPQ.

Please guide me if anything wrong.

Regards

Sowmya

vijay_kumar49
Active Contributor
0 Kudos

this sso is logonticket or userid/password type?

sowmya_m3
Explorer
0 Kudos

This is Logonticket Type..

Regards

Sowmya

vijay_kumar49
Active Contributor
0 Kudos

Do check the validity from and to Date of the certificate.  Also these are the steps to export the Portal Certificate.

Download a portal server certificate ( equivalent to verify.der ) as a ZIP file under portal

1. Logon to R3

2. Enter Tcode - STRUSTSSO2

3. Double click owner certificate. - The certificate gets reflected under the 'CERTIFICATE' TAB.

4. Click Export Certificate. (Left to 'ADD Certificate List)

5. Choose Format Binary

6. Choose file export path and enter a file name and save to your local drive.

You have to double click the owner certificate and not some certificate in the certificate list. Please do verify these steps.

sowmya_m3
Explorer
0 Kudos

Hi Vijay,

This PortalVersion: "7.31". Certificates validation date is not expired.

And when i download the CErtificate from Portal nwa, it is in .crt format.

Same file i have exported and followed the steps mentioned.

vijay_kumar49
Active Contributor
sowmya_m3
Explorer
0 Kudos

Hi Vijay,

I have downloaded new file as mentioned,

  1. SelectSAPLogonTicketKeypair-certfrom the list of available view entries.
  2. ChooseExport Entry.
  3. ChooseBinary X.509 Certificate File
  4. for the download format.                                                                                                                                                                                                                 

While importing this is giving Error Message Trust008, since the certificate already added

vijay_kumar49
Active Contributor
0 Kudos

check with BASIS people

sowmya_m3
Explorer
0 Kudos

Dear Vinay,

Thanks for giving try, ill check with Basis team, Am getting another error : Cannot connect to the provider in UWL. Who has to do the RFC destination connections? Basis people or Portal consultant?

vijay_kumar49
Active Contributor
0 Kudos

RFC destination connections means SLD and JCO's

vijay_kumar49
Active Contributor
sowmya_m3
Explorer
0 Kudos

i have gone through all the links, Since RFC Destinations are already created , am just verifying it.

Here SLD connections are working fine. JCO are not working because of SSO.

Now the main issue is SSO. Not able to find the solution for this