SWU0 Simulation of an event
Personalisation of role in PFCG / user in SU01
The second component of the application layer is the message server. It acts as a kind of "mediator" between the services and the applications.
Mentioning the SUM tool leads us to another part of SAP Basis: system updates and upgrades. Since SAP software receives updates from SAP at regular intervals - in the case of R/3 in the form of SPS (Support Package Stacks) and in the case of S/4HANA in the form of FPS (Feature Pack Stacks) - a large part of an SAP Basis administrator's job is to import these packages into the SAP system.
CG3Y File download
This makes the technical user the dialogue user and a login in the SAP system is unrestricted. So Johannes logs in with the known password of the RFC user in the production system. Thanks to very extensive permissions, it now has access to all sorts of critical tables, transactions, and programmes in production. With the identity of the RFC user Johannes starts with the technical compromise of the production system... RFC Security: All invented - or everyday threat? Whether a simple trim, altered biometric properties or an encapsulated technical user in the SAP system: the basis of the compromise is the same. A person uses a different identity to gain access and permissions to protected areas. Moreover, the evil in all three stories could have been prevented by pro-activity. When was the last time you thought about the security of your RFC interfaces? Can you say with certainty that all your technical RFC users only have the permissions they actually need? And do you know who exactly knows the passwords of these users? Can you 100% rule out that not now in this moment an SAP user with a false identity infiltrates your production systems? Change now: It's about pro activity! But before you start now and start looking for the "identity converter" (which I really do not recommend!), I suggest that you take root of evil and proactively strengthen your RFC security. So if you want to find out more, I have the following 3 tips for you: 1) Our e-book about SAP RFC interfaces 2) Clean up our free webinar about RFC interfaces 3) Blog post about our approach to optimising RFC interfaces As always, I look forward to your feedback and comments directly below these lines!
On www.sap-corner.de you will also find useful information about SAP basis.
If all tasks considered to be an interface theme are supported by the SAPBasis, this means a very wide range of tasks. Here it is necessary not to overwhelm the own employees within the SAP basis and to keep the complexity of different topics and technologies manageable per capita. Therefore, a corresponding growth is associated with this interface task. This recommendation is general and does not apply only to the SAP basis.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Using the gateway as a proxy Since the gateway of your SAP system can also serve as a proxy server, the prxyinfo ACLDatei should also be activated via the gw/prxy_info parameter.
Option 2: Logging-based approach An alternative to the restrictive procedure is the logging-based approach.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.