Accessing Data Using Secure Network Communications

The SAP system and the RFC protocol support secure network communications (SNC). You can configure SNC to enable single sign-on (SSO). Although you can also use SNC without single sign-on, you must still include user name and password credentials. This section shows two examples of how to specify the SNC logon information with the SAP LIBNAME engine. You must configure the SAP system and user accounts for SNC. For information about how to do this, see the SAP document, Secure Network Communications User's Guide.

This method requires that you create an entry in the saprfc.ini file. Here is an example:

DEST=SI9
TYPE=A
ASHOST=sapr3srv.sup.com
SYSNR=03
SNC_MODE=1
SNC_PARTNERNAME=p:SAPServiceSI9@sup.com
SNC_LIB=C:\Public\win32sso\gssntlm.dll

Then, use the LIBNAME statement to use the connection:

libname a r3 dest=SI9;  

You can also use the RFC_STRING option to apply additional settings:

 libname a r3 ashost=sapr3srv.sup.com sysnr=03 
    rfc_string="SNC_MODE=1 SNC_PARTNERNAME=p:SAPServiceSI9
    SNC_LIB=C:\Public\win32sso\gssntlm.dll";  

The SNC_LIB string must not contain blanks.

This document shows two examples of how to use SNC for single sign-on in a LIBNAME statement. For more information about SNC and SNC configuration, see SAP documentation and other third-party documentation.