How to Creating the SAP Router certificate

Creating the SAP Router certificate request

1. Login to the SAP Service Marketplace with the S-user ID which is assigned to your installation.
2. Use the latest SAProuter version, which can be downloaded from the SAP Software Download Center at http://service.sap.com/swdc.
3. Change to http://service.sap.com/saprouter-sncadd. Before you can download the software components two preconditions must be met:
   1. You must have been allowed to download the software. This authorization is added as soon as SAP has received a positive statement from the "Bundesausfuhramt" (German Federal Export Office). This procedure is necessary since the software falls under EU regulations.
      For more information on how to obtain authorization if download is not possible see note 397175.
      
   2. You must accept that you must follow the regulations imposed by the EU on the use and distribution of the cryptographic software components downloaded from the SAP Service Marketplace.
      The acceptance of the terms and conditions is logged with your user ID and stored for reporting purposes to the "Bundesausfuhramt".
4. Click on "Download Area" > "SAP Cryptographic Software" and select the correct sapcrypto library for your SAProuter <op-sys>. Save the file to the directory where the SAProuter executable is located.
5. You can get the file car.exe/sapcar.exe, which is necessary to unpack the archive from any Installation Kernel CD. Executing the command car -xvf SAPCRYPTO.CAR will unpack the following files:
   • [lib]sapcrypto.[dll|so|sl]
   • sapgenpse[.exe]
   • ticket

Creating the certificate request

1. As user <snc_adm> set the environment variables SNC_LIB and SECUDIR:
   

UNIX
SECUDIR = <directory_of_SAProuter>
SNC_LIB = <path_to_libsecude>/<name_of_sapcrypto_library>
Windows NT, 2000, XP or higher
SECUDIR = <directory_of_SAProuter>
SNC_LIB = <drive>:\<path_to_libsecude>\ntia64\sapcrypto.dll or
SNC_LIB = <drive>:\<path_to_libsecude>\ntintel\sapcrypto.dll or
SNC_LIB = <drive>:\<path_to_libsecude>\nt-x86_64\sapcrypto.dll
Note
After configuring the variables in Windows, you have to reboot this server before you continue.

Change to http://service.sap.com/saprouter-sncadd. From the list of SAProuters registered to your installation, choose the relevant "Distinguished Name".

Generate the certificate Request with the command:
sapgenpse get_pse -v -r certreq -p local.pse "<Distinguished Name>"

Example:

sapgenpse get_pse -v -r certreq -p local.pse "CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE"

Alternatively use the two commands:
sapgenpse get_pse -v -noreq -p local.pse "<Distinguished Name>"
sapgenpse get_pse -v -onlyreq -r certreq -p local.pse

You will be asked twice for a PIN here. Please choose a PIN and document it, you have to enter it identically both times. Then you will have to enter the same PIN every time you want to use this PSE.

Display the output file "certreq" and with copy & paste (including the BEGIN and END statement) insert the certificate request into the text area of the same form on the SAP Service Marketplace from which you copied the Distinguished Name.

In response you will receive the certificate signed by the CA in the Service Marketplace. Copy & paste the text to a new local file named "srcert", which must be created in the same directory as the sapgenpse executable.

With this in turn you can install the certificate in your SAProuter by calling:

sapgenpse import_own_cert -c srcert -p local.pse

Now you will have to create the credentials for the SAProuter with the same program (if you omit -O <user_for_SAProuter>, the credentials are created for the logged in user account).

sapgenpse seclogin -p local.pse -O <user_for _SAProuter>
Note: The account of the service user should always be entered in full <domainname>\<username>

This will create a file called "cred_v2" in the same directory as "local.pse"

For increased security please check that the file can only be accessed by the user running the SAProuter.
Do not allow any other access (not even from the same group)!
On UNIX this will mean permissions being set to 600 or even 400!
On Windows check that the permissions are granted only to the user the service is running as!

Check if the certificate has been imported successfully with the following command:

sapgenpse get_my_name -v -n Issuer
The name of the Issuer should be:
CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE

If this is not the case, delete the files "cred_v2"and "local.pse" and start over at item 3. If the output still does not match please open a customer message at component XX-SER-NET stating the actions you have taken so far and the output of the commands 3.,6.,7. and 9.