Question:
Hi,
Two questions
(1)
In v4.x systems where the security audit log exists, we have the ability to apply a fliter logging successful / unsuccessful RFC calls, and subsequent reporting.
However in our older v3.x systems where this functionality does not exist, I was wondering if anyone had an idea how we might achieve a similar effect (log/report).
Reason is Security related (detective report needed for less-than-ideal S_RFC restriction), but I assume the answer may be a bit more Basis / ABAPer related...
(2) I dont understand the SAP help on the paramater auth/rfc_authority_check with regards to setting 1 and 2 - how does the "same user context" work...Any ideas welcome.
Thanks and Regards,
DANIEL
Answer:
...Any ideas welcome.
Thanks and Regards,
DANIEL
Dear Daniel,
It appears to be difficult to answer you question without giving away secrets.
Some here say: "The heart has its reasons which reason knows not of"
Just click wildly around and maybe you hit the spot.
Bob
Answer:
I'll try again.
Regarding the parameter: Read the documentation on the object S_RFC. (transaction SU21) together with the parameter documentation.
Regarding the control: Does 3.1X have ST01 trace that can trace RFC Calls? That is however not a permanent solution.
Hope this was more helpfull than clicking around
Cheers,
Bob
Answer:
You can also search for CALL_FUNCTION_SIGNON_REJECTED in OSS.
Regards,
Bob