Show TOC

Background documentationAdministration When Using SNC for Single Sign-On Locate this document in the navigation structure

 

You can use Secure Network Communications (SNC) for Single Sign-On for applications that run in an ABAP environment and use the SAP GUI for Windows as the frontend client. Along with the SSO feature, SNC also provides protection at the transport layer.

Prerequisites

SNC is configured on the SAP system.

Restrictions
  • SNC requires the use of a security product to provide protection. There is a default product provided by SAP, the SAP Cryptographic Library, however, you cannot use this library for user authentication and Single Sign-On. For user authentication and Single Sign-On, you must use a security product that has been certified for use by the SAP Software Partner program.

  • SNC is available for the SAP protocols, RFC and DIAG. Therefore, the use of SNC for user authentication and Single Sign-On is only available for ABAP-based systems where the frontend access uses either SAP GUI for Windows or RFC.

Tasks on Demand

The tasks involved with SNC are primarily configuration, however, when you create a new user you must also maintain his or her SNC name. For more information, see the SNC Tab Page in user administration (transaction SU01).

Note Note

The user's SNC name is stored in the table USRACL, therefore, as an alternative, you can schedule the report RSUSR300 to fill this table automatically on a regular basis.

End of the note.

See also:

SNC is also used to secure data communications at the transport layer. Therefore, when using SNC, also see Administration Tasks for Cryptographic Services and Transport Layer Security.

For the SNC configuration, see Secure Network Communications (SNC).