Manual Config HttpsConnections NEWOSS
Manual Config HttpsConnections NEWOSS
Manual Config HttpsConnections NEWOSS
2022 - Document updated to match latest configuration (Short: instead of SSL Client (Standard),
SSL Client (Anonymous) is used)
(Mitigation for releases 7.00 to 7.31: still old RFC SAPOSS destination can be used, but the destination
must be switched to technical S-User (sm59, select destination, change user/password))
This document explains in detail what several task of the of task list SAP_BASIS_CONFIG_OSS_COMM
are doing automatically that they can be performed manually in the system.
The automated configuration is all about enabling the system for SSL and create three https
destinations:
Checks for correct cryptolib version that you can enable ssl at all on your system
Execute
In case version of SAPcryptolib is too low, follow SAP Note 2450794 - How to update CommonCryptoLib
in a NetWeaver ABAP system
Task 2: New OSS: Check TLS prot. version >= TLSv1.1 w.BEST-OPTION (RZ11)
Checks if the profile parameter ssl/client_ciphersuites is set correctly to enable ssl (TLSv1.2)
Click Display
In case the parameter is not set start transaction rz10 and set the profile parameter.
More details about setting TLS version, can be found in SAP Note 510007 - Setting up SSL on Application
Server ABAP
Task 3: New OSS: Check Certificates for SSL Client (STRUST)
Checks if all necessary certificates for SSL Client (Anonymous) is in the list
Check in the certificate list that the following certificates are available and valid:
In case the entry SSL Client SSL Client (Anonymous) is not created and certificates are not available:
https://www.digicert.com/digicert-root-certificates.htm
Connection Type: H
Host: apps.support.sap.com
Port: 443
Language: EN
Client: 001
SSL: Active
Connection Type: G
Host: documents.support.sap.com
Port: 443
SSL: Active
Connection Type: G
Host: notesdownloads.sap.com
Port: 443
SSL: Active
The 404 response is ok. When in SNOTE a note is downloaded the path to the note is added to the
request like /note/0040000000874972019.
For a 200 response you can copy the created destination and enter the string to the Path Prefix field and
perform a connection test.
With latest update a new task in task list was introduced that enables SNOTE to use the created
destinations. This can be checked/set by executing transaction: CWB_SNOTE_DWNLD_PROC and select
HTTP Protocol
Troubleshooting:
Connection issues:
in case you experience connection issues, the ICM trace (TA: SMICM) can give valuable
information;
contact your network admin that the https requests can get out of your company network
(router, port settings, whitelist, blacklists in firewall, etc.)
in case you are using a sap router string in front of the host and you have the SM59 https proxy
setting active (check in menu of SM59), you must add the host in the filter list; in this case the
host contains already the route it should NOT go the global proxy again; on top of that the https
proxy setting is client independent
Authentication issues:
The standard S-User will not work for the OSS connections, you need to use a technical S-User.
You can request a technical user here: https://apps.support.sap.com/technical-user/index.html
If you are using a technical S-User and still get authentication issues, it could be that the user is
locked. In this case contact Support that they can unlock the technical S-User
Further resources:
How to test https connection for SAP Note download after the execution of task list
SAP_BASIS_CONFIG_OSS_COMM: https://launchpad.support.sap.com/#/notes/2836996