Parameter
snc/only_encrypted_rfc
Short text
Force encrypted RFC connections
Parameter Description
If this parameter is set to a value other than “0”, unencrypted RFC connections are rejected with an error message.
If the parameter value is “1”, only unencrypted RFC connections that are requested by external (non-ABAP) RFC clients are rejected. Connections requested by ABAP programs can be unencrypted.
If the parameter value is “2”, only internal unencrypted RFC connections (within the same logical system) are accepted. All RFC connections from external RFC clients (ABAP and non-ABAP) must be encrypted.
If the parameter value is “3”, all RFC connections (including internal connections) need to be encrypted.
To encrypt RFC connections, an SNC product with the QoP setting “Encryption” is required. Selecting a lower QoP level (such as “Integrity”) is not sufficient to fulfill the required condition.
Unlike profile parameter snc/accept_insecure_rfc, this profile parameter does not control whether a user can log on with a password, or must log on using SNC. The two parameters can be used in combination and extend each other meaningfully.
Application Area
SNC
Default Value
0
Are other parameters affected or dependent?
snc/enable
snc/accept_insecure_rfc
snc/r3int_rfc_secure
snc/r3int_rfc_qop
Values allowed
0 / 1 / 2 / 3
