|
Parameter Short text Parameter description
If callbacks have been forbidden by a previous call of the functionmodule RFC_CALLBACK_REJECTED, the callback is rejected. Otherwise, thecallback is executed. All whitelist entries for RFC callbacks (including the active entires)are ignored. If callbacks have been forbidden by a previous call of the functionmodule RFC_CALLBACK_REJECTED, the callback is rejected. If the callback is forbidden by an active whitelist, it is rejected. In all other cases, the callback is permitted. Every permitted callback is logged in the Security Audit Log with a"non-critical" (green) entry. Every rejected callback is logged with a"critical" (red) entry. If callbacks have been forbidden by a previous call of the functionmodule RFC_CALLBACK_REJECTED, the callback is rejected. If the callback is forbidden by an active whitelist, it is rejected. In all other cases, the callback is permitted. Every rejected callback is logged with a "critical" (red) entry in theSecurity Audit Log. Every permitted callback, which would have beenrejected if the whitelist had been activated, is also logged with a"critical" (red) entry in the Security Audit Log. All other permittedcallbacks are logged with a "non-critical" (green) entry. If callbacks have been forbidden by a previous call of the functionmodule RFC_CALLBACK_REJECTED, the callback is rejected. If the callback is forbidden by an active or inactive whitelist, it isrejected. (Note that, in this mode, an inactive whitelist has the sameeffect as an active whitelist.) In all other cases, the callback is permitted. Every rejected callback is logged with a "critical" (red) entry in theSecurity Audit Log. Every permitted callback is logged with a"non-critical" (green) entry. Work area Parameter unit Who is allowed Limitation for os Limitation for db Other parameter Valid_values |