Skip to Content
avatar image
Former Member

Principal Propagation

using principal propagation in the scenario SOAP - XI - RFC

If a message from RWB, the <userid> is accessing the RFC function

If a message is sent from external SOAP client, PIAFUSER is accessing the RFC function

The expected result is to use <userid> from external SOAP client to access the RFC function

Any ideas are appreciated

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 02, 2007 at 02:08 PM

    Hi !

    Check this blog:

    /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi

    and this document (requiers service marketplace user):

    https://smpdl.sap-ag.de/~sapidb/012006153200000218192007E/PrincipalPropagation_SP19_SP10.pdf

    Regards,

    Matias.

    Message was edited by:

    Matias Denker

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Soap client in our scenario is VisualStudio.Net.

      Everything works when the principal Propagation checkbox is not checked in the sender and receiver agreements.

      The userid hardcoded in the RFC adapter is sent to the backend SAP system.

      So I think the problem may not be with the SOAP Client.

      The thing that is confusing is, If there is something wrong in the Principal Propagation configuration, why the RFC adapter is sending the PIAFUSER instead of the hardcoded userid in the Communication Channel

      Thanks

  • avatar image
    Former Member
    Jul 07, 2015 at 04:47 PM

    Hi,

    Were you able to flow your user thru the entire process, not just PIAFUSER?

    Thanks!

    Add comment
    10|10000 characters needed characters exceeded