cancel
Showing results for 
Search instead for 
Did you mean: 

SSO does not work even after everything is configured correctly!!

former_member190996
Participant
0 Kudos

Hello,

I have configured the SSO successfully between portal and ECC several times before but not this time. Though I have maintained all the parameters correctly I could not get the system object to connect successfully. Below is what I have done:

  • Maintained the services files on both portal (SID: DP4) and ECC (SID: PS1) servers with the below entries:
sapmsPS13600/tcp
sapmsDP43901/tcp
  • Registered the JCo RFC provider on Portal and created the RFC destination (PS1_DP4_Connector) on ECC. Also tested successfully:

  • Exchanged the certificates between Portal and ECC:

Portal Certificate in ECC:

ECC certificate in Portal:

  • System Object connection tests fails as below. All the ports are opened, and the telnet is working fine on 8001 and 3600.

  • I see the below errors on the diagtool trace:

The message server is not reached and complaining about the logon group as well. Any ideas on what am I missing here?

Regards,

SB

Accepted Solutions (0)

Answers (3)

Answers (3)

nickrankin
Contributor
0 Kudos

Please check SAP Note: 2037383 which deals with error "ERROR Group PUBLIC not found"

Nick

former_member190996
Participant
0 Kudos

The logon groups were maintained in the SMLG and also in the SLD for the technical system. Still the error persists. I guess there is an issue with the gateway/load balancing configuration.

former_member190996
Participant
0 Kudos

Any suggestions on further debugging the issue?

nickrankin
Contributor
0 Kudos

Hi SB,

The stack trace you attach is referencing a WebDynpro and may not be related to your SSO issue. Are there any Security errors written to the backend Work Processes trace? AL11 transaction -> work folder. You can use transaction SM50 to set Security component tracing severity to "3", to get more detailed Security traces

Nick

former_member190996
Participant
0 Kudos

Hi Nick,

The trace is after replicating the SSO issue by accessing the webdynpro java application that uses the JCOs to access the data from the backend. Those JCOs are using the SSO as logon method, but failing with the below error. I do not see anything in the SM50. Can you please be more specific?

Error:

com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connection parameters: TYPE=B DEST=<Java Rfc client> MSHOST=ecerpp00 R3NAME=PS1 GROUP=PUBLIC PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode ERROR Group PUBLIC not found TIME Thu Jan 03 22:54:30 2019 RELEASE 721 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 5351 DETAIL LgIGroupRereadMs COUNTER 82