This means that the order of the rules is very important, especially when general definitions are being used (“TP=*”) All subsequent rules are not even checked. The RFC Gateway will apply the rules in the same order as they appear in the file, and only the first matching rule will be used (similar to the behavior of a network firewall).Each line must be a complete rule (you cannot break the rule into two or more lines).The very first line of the reginfo/secinfo file must be "#VERSION=2".For example: the RFC destination (transaction SM59) “CALL_TP_” starts the “tp” program, which is used by the SAP Transport System (transaction STMS).īefore jumping to the ACLs themselves, here are a few general tips: In other words, the SAP instance would run an operating system level command. The secinfo file has rules related to the start of programs by the local SAP instance. For example: an SAP SLD system registering the SLD_UC and SLD_NUC programs at an ABAP system. The reginfo file have ACLs (rules) related to the registration of external programs (systems) to the local SAP instance. This section contains information about the RFC Gateway ACLs, and examples of landscapes and rules. Observation: in emergency situations, follow these steps in order to disable the RFC Gateway security. This page contains information about the RFC Gateway ACLs (reginfo and secinfo files), the Simulation Mode, as well as the workflow showing how the RFC Gateway works with regards to the ACLs versus the Simulation Mode.Īdditional ACLs are discussed at this WIKI page. Help with the understanding of the RFC Gateway ACLs (Access Control Lists) and the Simulation Mode, in order to help prepare production systems to have these security features enabled without disruptions.
0 kommentar(er)
