test

Configuring Secure Network Communications for SAP

Chapter 1 Configuring Secure Network Communications for SAP

The following section provide instructions on how to configure Secure Network Communications (SNC) for the SAP System architecture. SNC provides an interface to an external security product for . SAP Systems, allowing basic security measures like SAP authorization and user authentication based on passwords. If you have any questions or problems, see the Java CAPS web site at http://goldstar.stc.com/support.

This chapter covers the following information:

Configuring Secure Network Communications for SAP

Secure Network Communication (SNC) is a software layer in the SAP System architecture that provides an interface to an external security product. SAP Systems provide basic security measures like SAP authorization and user authentication based on passwords.

With SNC you can include protection by an external security product. SNC provides application-level, end-to-end security. It secures all communications between two SNC-protected components. For example, between SAPGUI and a SAP System Application Server. SNC protection only applies to connections that use SAP protocols (dialog, RFC or CPIC protocols). For example from a SAP Application System Server to an External RFC or CPIC program like SAP Java Connector.

SNC secures the data communication paths between the various SAP System components. There are three levels of security protection you can apply.

Communication using Secure Network Communications

SNC protects the logical link between the end points of a communication. The link is initiated from one side (the initiator) and accepted by the other side (the acceptor). For example, when a SAPGUI starts a dialog with the SAP System, the SAPGUI is the initiator of the communication and the application server is the acceptor. Both sides of the communication link need to specify SNC options.

The initiator must specify:

Table 1–1 SNC Parameters (Outbound)

Name 

Description 

Value 

SNC_MODE 

The SNC activation indicator. 

  • 0 — Do not apply SNC to connections.

  • 1 — Apply SNC to connections.

SNC_MYNAME 

The Initiator's SNC name. 

A valid SNC name. 

SNC_PARTNERNAME 

The communication partner's SNC name. 

A valid SNC partner's name. 

SNC_QOP 

The quality of protection level. 

Enter one of the following values: 

  • 1 — Apply authentication only.

  • 2 — Apply integrity protection (authentication).

  • 3 — Apply privacy protection (integrity and authentication).

  • 8 — Apply the default protection.

  • 9 — Apply the maximum protection.

SNC_LIB 

The external security product's library. 

The path and filename of the library. 

The acceptor must specify:

Table 1–2 SNC Parameters (Inbound)

Name 

Description 

Value 

SNC_MYNAME 

The Acceptor's SNC name. 

A valid SNC name. 

SNC_QOP 

The quality of protection level. 

Enter one of the following values: 

  • 1 — Apply authentication only.

  • 2 — Apply integrity protection (authentication).

  • 3 — Apply privacy protection (integrity and authentication).

  • 8 — Apply the default protection.

  • 9 — Apply the maximum protection.

SNC_LIB 

The external security product's library. 

The path and filename of the library. 

When SNC is initialized, the system dynamically loads the functions provided by the external library. Afterwards, when two components communicate using SNC, the SNC layer first processes the messages being sent and then sends them over the network using the SAP Network Interface. During this step, the SNC layer uses the functions provided by the external library to process the messages accordingly (for example, to apply encryption). The SNC layer accesses the external library using the GSS-API V2 interface. After processing the messages, the system sends them over the SAP Network Interface in the usual manner. Upon receipt, the SAP System component receiving the messages applies the corresponding external library functions in a similar manner, but reverses the process (for example, decryption)

For example when secure network communication occurs between SAPGUI and the SAP Server (where SNC is already enabled) sapgui.exe hs0017 01 SNC_PARTNERNAME="p:CN=sap01.hs0017, OU=TEST01, O=SAP, C=DE" SNC_QOP=9 SNC_LIB="C:\SECUDE\LIB\SECUDE.DLL"

The connection is established to the application server hs0017. The application server's SNC name is: p:CN=sap01.hs0017, OU=TEST01, O=SAP, C=DE. The level of protection is 9, indicating that the maximum level of protection should be applied to the connection, and the shared library is located at: C:\SECUDE\LIB\SECUDE.DLL.

Setting up Secure Network Communications on the SAP Server

The following sections cover the installation and configuration of SNC.

ProcedureTo Install the SAP Cryptographic Library

  1. Extract the contents of the SAP Cryptographic Library installation package.

  2. Copy the library file and the configuration tool (sapgenpse.exe) to the directory specified by the application server's profile parameter DIR_EXECUTABLE.

    In the following example, this directory is represented with the notation $(DIR_EXECUTABLE).

    Windows NT:

    • DIR_EXECUTABLE: <DRIVE>:\usr\sap\<SID>\SYS\exe\run\

    • Location of SAP Cryptographic Library: <DRIVE>:\usr\sap\<SID>\SYS\exe\run\sapcrypto.dll

  3. Check the file permissions for the SAP Cryptographic Library. Make sure that <sid> adm (or SAPService <SID> under Windows NT) is able to execute the library's functions.

  4. Copy the ticket file to the sec sub-directory in the instance directory $(DIR_INSTANCE).

    Windows NT:

    • DIR_INSTANCE: <DRIVE>:\usr\sap\<SID>\<instance>

    • Location of the ticket: <DRIVE>:\usr\sap\<SID>\<instance>\sec\ticket

  5. Set the environment variable SECUDIR to the sec sub-directory.

    The application server uses this variable to locate the ticket and its credentials at run-time. If you set the environment variable using the command line, then the value may not be applied to the server's processes. Therefore, setting SECUDIR in the start-up profile for the server's user or in the registry (Windows NT) is recommended.

    Note –

    These instructions are available at http://help.sap.com/saphelp_erp2004/helpdata/en/96/709b3ad94e8a3de10000000a11402f/frameset.htm

ProcedureTo Create the PSE for Server

  1. Start transaction RZ10 and select the instance profile used by the server start-up.

  2. Add the instance parameter "snc/identity/as".

  3. Set the instance parameter "snc/identity/as" to the specific name of the server.

    For example: "snc/identity/as p:CN=IDS, OU=IT, O=CSW, C=DE" (Do not forget to add "p:" in front of the name, as shown below).

    Note –

    While specifying the distinguished name for your Client/Server PSE "CN=xx, OU=xx, O=xx, C=xx", the cryptographic tool validates the country code for the "C=xx" attribute.

    Active Parameter Name and Value

    This example shows an X.500 Name. It is formed from different elements that represent a hierarchical name space. Where CN = Common Name, OU = Organizational Unit, O = Organization and C = Country.

  4. Restart your server.

    After restarting your server you can now create the SNC PSE.

  5. Start the STRUST transaction, right click on "SNC (SAPCryptolib)," and choose Create.

  6. Accept the SNC ID which is taken from the instance parameter "snc/identity/as."

  7. Double click "SNC (SAPCryptolib)" and choose "Assign Password" to add a password for the "SNC (SAPCryptolib)" PSE.

  8. Type in a password.

    The Password can contain both letters and numbers. Without the password the server would not start when you set the instance parameter "snc/enable" to 1.

  9. Save the settings.

ProcedureTo Set Additional Parameters

  1. Start transaction RZ10 and select the instance profile used by the server start-up.

    Edit Profiles

  2. Set the parameters as listed in the table below.

    Parameter 

    Description 

    Value 

    snc/enable 

    Activates SNC on the application server. 

    Default value is 1. 

    snc/gssapi_lib 

    The path and file name of the GSS-API V2 shared library. Path and file name where the SAP Cryptographic Library is located. 

    • For UNIX: usr/sap/<SID>/SYS/exe/ run/libsapcrypto.so

    • For Windows NT: D:\usr\sap\<SID> \SYS\exe\run\sapcrypto.dll

    snc/identity/as 

    The SNC name of the application server. 

    Syntax: p:Distinguished_Name> The <Distinguished Name part must match the Distinguished Name that you specify when creating the SNC PSE. For example p:CN=ABC, OU=Test, O=MyCompany, C=US

    snc/data_protection/max 

    The maximum level of data protection for connections initiated by the SAP System. 

    The maximum level of data protection settings: 

    • 1: Authentication only

    • 2: Integrity protection

    • 3: Privacy protection

    snc/data_protection/min 

    The minimum data protection level required for SNC communications. 

    The minimum level of data protection settings: 

    • 1: Authentication only

    • 2: Integrity protection

    • 3: Privacy protection

    snc/data_protection/use 

    Default level of data protection for connections initiated by the SAP System 

    The default level of data protection settings: 

    • 1: Authentication only

    • 2: Integrity protection

    • 3: Privacy protection

    • 9: Use the value from snc/data_ protection/max

    snc/accept_insecure_cpic 

    Determines if unprotected incoming CPIC connections on an SNC-enabled application server will be accepted or not. 

    The settings for accepting CPIC connections: 

    • 0: do not accept

    • 1: accept

    snc/accept_insecure_gui 

    Determines if logon attempts coming from the SAP interface that are not protected with SNC on an SNC-enabled application server will be accepted or not. 

    The settings for accepting logon attempts: 

    • 0: do not accept

    • 1: accept

    snc/accept_insecure_r3int_rfc 

    Determines if unprotected internal RFC-connections on an SNC-enabled application server will be accepted or not. 

    The settings for accepting unprotected internal r3int RFC-connections: 

    • 0: do not accept

    • 1: accept

    snc/accept_insecure_rfc 

    Determines if unprotected internal RFC-connections on an SNC-enabled application server will be accepted or not. 

    The settings for accepting unprotected internal RFC-connections: 

    • 0: do not accept

    • 1: accept

    snc/permit_insecure_start 

    Permits the starting of programs without using SNC-protected communications, even when SNC is enabled. 

    The settings to permit the starting of programs: 

    • 0: do not allow

    • 1: allow

    snc/extid_login_diag 

    		 

    • 0: do not accept

    • 1: allow

    snc/extid_login_rfc 

    		 

    • 0: do not accept

    • 1: allow

    Setting the profile parameter snc/enable to 1 activates SNC on the application server. If this parameter is set but the SNC PSE and credentials do not exist, then the application server will not start. Therefore, setting the SNC parameters should be the last step in the configuration procedure.

    These values will enable you to connect to the system without encryption.

  3. Save the settings.

  4. Restart the application server again.

Profile Parameter Settings on the Gateway

To use SNC for securing connections that connect via the SAP gateway, you also need to set the appropriate parameters in the gateway profile. The gateway itself does not directly use the routines from the security product; however, it does supply the SNC configuration parameters to the programs that it starts. Release 3.1 does not offer SNC protection for the RFC and CPIC communication protocols. In Release 3.1, you need to set the profile parameter snc/permit_insecure_comm to the value "1".

Note –

The rest of the description in this section applies only as of Release 4.0.

The following profile parameters are relevant for the gateway settings:

ProcedureTo Create PSE for the Client

  1. Create a directory on your system to store the PSE.

  2. Copy the ticket license file and the SAP Certified Client Cryptographic library (ex. SECUDE) to the directory you just created.

    Make sure you set the SECUDIR environment variable to this directory, copy the library to a different directory, and add this path to your "PATH" environment variable.

  3. Execute the following command to generate the PSE

    The client PSE is named as RFC.pse. From the command line, you can specify the distinguished name. For example: "CN=RFC, OU=IT, O=CSW, C=DE"

    > sapgenpse gen_pse -v -p RFC.pse

    Got absolute PSE path "<your path>/RFC.pse".

    Please enter PIN: ********

    Please reenter PIN: ********

    get_pse: Distinguished name of PSE owner: CN=RFC, OU=IT, O=CSW, C=DE

    Supplied distinguished name: "CN=RFC, OU=IT, O=CSW, C=DE"

    Generating key (RSA, 1024-bits) ... succeeded.

    certificate creation... ok

    PSE update... ok

    PKRoot... ok

    Generating certificate request... ok.

    PKCS#10 certificate request for "<your path>/RFC.pse"

  4. Execute the following command to export the Client Certificate of the newly created PSE.

    The exported certificate is named as RFC.crt.

    > sapgenpse export_own_cert -v -p RFC.pse -o RFC.crt

    Opening PSE your path>/RFC.pse"...

    No SSO credentials found for this PSE.

    Please enter PIN: ********

    PSE open ok.

    Retrieving my certificate... ok.

    writing to file ...... ok

  5. Import the Client Certificate to Server PSE.

    You can import the client Certificate via Transaction STRUST.

    1. Open the Node SNC (SAPCryptolib) again

    2. Enter the SAPCryptolib password.

    3. Click on the Import certificate button.

    4. Set the file format to Base64 and choose the file

    5. Click Add to Certificate List

  6. Export the Server Certificate.

    Export the Server Certificate via the Transaction STRUST.

    1. At node SNC (SAPCryptolib), double click on your own certificate so it displays in the Certificate field.

    2. Click on Export certificate.

    3. From the File tab, choose Base64 for the File format and provide a name for the file.

  7. Import the Server Certificate to the Client PSE

    On the command line run:

    > sapgenpse maintain_pk -v -a SNC.crt -p RFC.pse

    Opening PSE your path>/RFC.pse"...

    No SSO credentials found for this PSE.

    Please enter PIN: ********

    PSE open ok.

    Adding new certificate from file "SNC.crt"

    ----------------------------------------------------------------------------

    Subject : CN=IDS, OU=IT, O=CSW, C=DE

    Issuer : CN=IDS, OU=IT, O=CSW, C=DE

    Serialno: 00

    KeyInfo : RSA, 2048-bit

    Validity - NotBefore: Wed Mar 6 21:37:32 2008 (060927193732Z)

    NotAfter: Fri Jan 1 01:00:01 2038 (380101000001Z)

    -----------------------------------------------------------------------------

    PKList updated (1 entries total, 1 newly added)

  8. Create the cred_v2 file.

    After setting up the client PSE you must create a file called cred_v2 which is used to securely give the RFC Program access to the PSE without providing the password for the PSE.

    On the command line run:

    > sapgenpse seclogin -p RFC.pse -O root running seclogin with USER="root"

    creatingcredentials for yourself (USER="root")...

    Please enter PIN: ********

    Added SSO-credentials for PSE "<your path>/RFC.pse"

    "CN=RFC, OU=IT, O=CSW, C=DE"

    Note –

    When you generate the cred_v2 file, the seclogin must be carried out under the account of the <sid>adm.

  9. Allow SNC RFC Connection.

    Now you need to map the x.509 certificates that were created for the user accounts on the SAP Server.

    1. Start Transaction SM30 and enter the view VSNCSYSACL.

      This view is used to restrict the SNC RFC Connections by an Access Control List (ACL). You will see an alert window pop-up, just click on the "right" symbol.

    2. Choose "E" for the Type of ACL entry.

    3. Enter System ID and SNC name.

      Note –

      Do not forget the "p:" in front of the DN.

    4. Check the boxes according to the following figure.

    5. Save the entry.

    Note –

    When trying to edit the entry, you might see an alert window pop-up. Just click on the "right" symbol and make your changes.

  10. Map the X.509 Certificate to the User.

    The X.509 Certificate must be accepted for a successful Login.

    1. Start Transaction SM30.

    2. Enter VUSREXTID and click Maintain.

      Using the view VUSREXTID, you can setup a mapping between the Distinguished Name provided by a X.509 Certificate and an ABAP User.

    3. Choose the Distinguished Name for the External ID type.

    4. Create a new entry and activate it.

Using Secure Network Communications in Java CAPS

Secure Network Communication connections are provided to the SAP Server during design-time and runtime in the SAP BAPI Adapter.

ProcedureTo Create a SAP BAPI OTD Using Secure Network Communications

  1. Begin creating a SAP BAPI OTD using the SAP BAPI OTD Wizard.

  2. At the step to Select Login Parameters, select the Enable SNCcheckbox.

  3. Specify the following parameters.

    • SNC Library Path: The path to the Security Library you are using, for example: <your drive>:/Secude/secude.dll

    • SNC Partner Name: The SNC Name you specified for the SAP Server (Server PSE), for example: p:CN=IDS, OU=IT, O=CSW, C=DE

    • X.509 Certificate: The certificate information of your Client PSE

    • SNC My Name: The name you specified for the Client PSE, for example: p:CN=RFC, OU=IT, O=CSW, C=DE

    The SNC Quality of Protection is defaulted to 1, since only authentication during the OTD creation is provided.

  4. Finish the SAP BAPI OTD Wizard.

    Note –

    You can connect to SAP Server without using SNC. Simply leave the Enable SNC checkbox disabled and only specify the enabled parameters.

ProcedureTo Create a SAP IDOC OTD Using Secure Network Communications

Secure Network Communication connections are provided to the SAP Server for SAP IDOC OTD creation, when you select the metadata source from the SAP directly option.

  1. Begin creating a SAP IDOC OTD using the SAP IDOC OTD Wizard.

  2. At the step to Select Login Parameters, select the Enable SNCcheckbox.

  3. Specify the following parameters.

    • SNC Library Path: The path to the Security Library you are using, for example: <your drive>:/Secude/secude.dll

    • SNC Partner Name: The SNC Name you specified for the SAP Server (Server PSE), for example: p:CN=IDS, OU=IT, O=CSW, C=DE

    • X.509 Certificate: The certificate information of your Client PSE

    • SNC My Name: The name you specified for the Client PSE, for example: p:CN=RFC, OU=IT, O=CSW, C=DE

    The SNC Quality of Protection is defaulted to 1, since only authentication during the OTD creation is provided.

  4. Finish the SAP IDOC OTD Wizard.

    During runtime, you can enable SNC for both outbound and inbound. You can specify the SNC parameters in the SAP BAPI External System.

    Note –

    You can connect to SAP Server without using SNC. Simply leave the Enable SNC checkbox disabled and only specify the enabled parameters.

Specifying SAP BAPI Outbound Properties

In the Outbound SAP BAPI eWay node, of the SAP BAPI External System properties window, a new Client Security Settings section has been created. You can specify the SNC properties in this section.

If you select Yes for the value of Enable SNC then you must specify the following parameters:

Note –

To use the values "8" or "9", you need to make sure you have set the instance parameters snc/data_protection/max and snc/data_protection/use during the SNC configuration on the SAP Server.

Specifying SAP BAPI Inbound Properties

In the Inbound SAP BAPI eWay node, of the SAP BAPI External System properties window, a new Server Security Settings section has been created. You can specify the SNC properties in this section.

If you select Yes for the value of Enable SNC then you must specify the following parameters:

Note –

To use the values "8" or "9", you need to make sure you have set the instance parameters snc/data_protection/max and snc/data_protection/use during the SNC configuration on the SAP Server.