Parameter
snc/only_encrypted_rfc

Short text
Enforce encrypted RFC connections

Parameter description
If this parameter is set to a value other than "0", unencrypted RFCconnections are rejected with an error message.
If the parameter value is "1", only unencrypted RFC connections that arerequested by external (non-ABAP) RFC clients are rejected. Connectionsrequested 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 fromexternal RFC clients (ABAP and non-ABAP) must be encrypted.
If the parameter value is "3", all RFC connections (including internalconnections) 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 "Inte
grity") is not sufficient to fulfill the required condition.
Unlike profile parameter snc/accept_insecure_rfc, this profile parameterdoes not control whether a user can log on with a password, or must logon using SNC. The two parameters can be used in combination and extendeach other meaningfully.

Work area
SNC

Parameter unit
Integer interval

Who is allowed
Customer

Limitation for os
None

Limitation for db
None

Other parameter
snc/enable
snc/accept_insecure_rfc
snc/r3int_rfc_secure
snc/r3int_rfc_qop

Valid_values
0 - 3