Enable SNC Module (Secure Network Communications)
If this parameter is set to "1", the work processes try toactivate/initialize the module SNC (Secure Network Communications) whenstarting up.
If security is activated, by default, all incoming connections areaccepted only if they are secure. If you want to permit conventionalconnections in parallel and use packet filtering routers to partitionthe R/3 system, you need to permit unsecure connections via additionalprofile parameters. In this case, you need to enter"snc/accept_insecure_gui = 1" for the GUI, for example, and "snc/ac
cept_insecure_rfc = 1" or snc/accept_insecure_cpic = 1" for RFC or CPICconnections.
The SNC module requires the file name (including the path) of the sharedlibrary of the external security product. When the SNC module isactivated, this shared library is loaded at runtime. (for example,"snc/gssapi_lib = /usr/local/lib/libsecude.so") If the shared librarycannot be found or loaded, or is not recognized, SncInit() returns theerror SNCERR_INIT and the work process terminates the process.
Who is allowed
Limitation for os
Limitation for db
- snc/gssapi_lib> path name of GSS-API sharedlibrary
- snc/identity/as> identity of the applicationserver at the external security system
- snc/accept_insecure_gui> permitconventional logon GUI
- snc/accept_insecure_rfc> permitconventional logon RFC
- snc/accept_insecure_cpic> permitconventional logon CPIC
- snc/data_protection/min> minimumrequirement to protect the data during transfer
- snc/data_protection/max> limit on theprotection of data during the transfer
- snc/data_protection/use> default valuefor the protection of outgoing connections
- snc/r3int_rfc_secure> secured connectionsalso for internal RFCs within the R/3 system
- snc/r3int_rfc_qop> protection levels forinternal RFCs
- snc/permit_insecure_start>permission for the gateway to also start unsecure programs
0 or 1