Communication Channel Security
This section provides an overview of network based communication paths and protocols used by SAP Landscape Management.
|
Communication Path |
Protocols Supported |
Type of Data Transferred |
Security Requirements |
|---|---|---|---|
|
SAP Host Agent |
HTTP HTTPS |
|
|
|
Instance Agent |
HTTP HTTPS |
|
|
|
Central name server communication Central user management |
LDAP LDAP over SSL |
|
|
|
Automatic synchronization based on the SAP Landscape Management export and import functionality |
HTTP HTTPS |
XML data files containing SAP Landscape Management configurations with system credentials. |
|
|
Java Post-Copy Automation (Java PCA) |
HTTP HTTPS |
Java PCA execution information containing confidential system information. |
|
|
SLD communication |
HTTP HTTPS |
Landscape information for discovery |
|
|
Remote Function Calls (RFC) on managed systems |
RFC |
System data such as passwords and PCA related data. |
You can apply the following levels of security protection:
|
|
SAP Solution Manager |
RFC |
|
|
|
Storage and virtualization adapters |
Depends on adapter implementation |
|
|
|
External tools accessing SAP Landscape Management web services or SAP Landscape Management Application Programming Interface (API) |
HTTP HTTPS |
|
|
|
REST services for SAPUI5, web services, and servlets |
HTTP HTTPS |
|
|
Dynamic Information and Action Gateway (DIAG) and RFC connections can be protected using Secure Network Communications (SNC). HTTP connections are protected using the Secure Sockets Layer (SSL) protocol. SOAP connections are protected with Web services security.
For more information, search for Transport Layer Security and Web Services Security in the SAP NetWeaver Security Guide.
