Trusted RFC: "jumping to PRD system from DEV"

[Former Member]

Hallo!

I have the following question regarding the Trusted RFC generally in SOLMAN area and better especially within ChaRM.

We have SOLMAN and 3 satellite systems DEV, QAS and PRD.

When we generate Trusted RFC connections from SOLMAN to these satellite systems, we become scared about the following scenario:

A user accesses to DEV system and goes via Trusted RFC to SOLMAN.

From SOLMAN he chooses the Trusted RFC to PRD system and goes into PRD system.

The question:

How can this identification gap/problem be solved?

Thank you very much indeed!

H. Thomasson

[Former Member]

Holger,

First of all the user that tries to launch the TRUSTED RFC needs to have an active user in the satellite system he/she tries to reach.

Secondly, this user needs to have the authorization object S_RFCACL assigned to its user.

You can manually change this TRUSTED RFC to 'Logon Screen' if you like.

Roel

[Former Member]

Hi Holger.

It's all about athorization. The user needs auth. object S_RFCACL in the target system. Without it he will not be able to use trusted rfc for system logon.

/cheers