Hi, we recently upgraded our kernel from 7.1 to 7.2 in our development system. Unfortunately, this has caused some griefs for our developers. They realize that all the programs that utilizes the RFC_REMOTE_PIPE rfc func. module is not working as it is returning a SYSTEM_ERROR exception all the time. They also realized by looking at the rfc trace file that is produced for every call that their failed calls did not pass the auth.check for rfcexec.
We look at the "permission file" rfcexec.sec and we notice the file format is totally different than 7.1's and it does not support wildcard. We are told that every O/S command that we would like to fire up from ABAP using the RFC_REMOTE_PIPE has to be listed per user per client in that file . THis is a huge deal and caught us off guard.
I was wondering if any one has had any experience in making this file work to allow users to call any O/S program without specifying one by one. I know it defeats the purpose of the permission file, but if you look at from the other side it is not practical and too cumbersome to specify every combination of OS command one by one per user and per client!!
Thanks in advance..
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.