Skip to Content
0

JCo Connector Fails to Connect with SNC Parameters

Aug 11, 2017 at 12:07 AM

66

avatar image
Former Member

We have a web application using the JCo connector that connects to our SAP system without a problem if we use username/password logons. However, our users log in to SAP via SSO where their X.509 certificate is used for authentication. We have an ADFS integration that passes the X.509 certificate to our application and we are attempting to authenticate against the same SAP system with SNC using the certificate instead of username/password. Our connection string is as follows:

"lang": "EN"

"sysid": "<OUR SYSID>"

"sysnr": "00"

"ashost": "<OUR IP ADDRESS>"

"client": "<OUR CLIENT #>"

"snc_qop": "1"

"snc_mode": "1"

"snc_partnername": "<OUR PARTNER NAME>"

"snc_lib": "/lib/sll/libsapcrypto.so"

We continue to get the following error messages when trying to connect to the system:

SncPEstablishContext() failed for target='<OUR PARTNER NAME>' [sncxxall_m 3386]

AND

RFC COMMUNICATION ERROR: RFC connection open failed / 1 / RFC_COMMUNICATION_FAILURE /
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR no conversation found with id 87591271
TIME Thu Aug 10 11:28:17 2017
RELEASE 720
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 473
MODULE r3cpic_mt.c
LINE 9215
COUNTER 8

I have a feeling, based on distant memories, that there might be a mismatch between the SNC_LIB on our web server and our SAP server, but I honestly don't know where to begin.

A potentially useful piece of information is that our SAP server runs on Windows while our web server runs on Linux.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
avatar image
Former Member Mar 26 at 03:11 PM
0

We solved this on our own. Our SAP system needed to be upgraded to allow SNC connections over RFC.

Share
10 |10000 characters needed characters left characters exceeded