Principal Propagation

[Former Member]

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

[Former Member]

Hi,

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

Thanks!

[Former Member]

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

[Former Member]

Hi Matias,

we configured the principal propagation based on the above two links. but something went wrong. Instead of propagating the logged on user, PIAFUSER is propogated. couldn't figure out why.

Thanks

[Former Member]

Hi !

check what Satish Reedy says in this thread:

Regards,

Matias.

[Former Member]

As the last message in the blog, I guess my question should be how to send an assertion ticket from the client to SAP.

some part of the principal propagation is working. the test from RWB -- Integration server -- Test Messages works. and test from RWB -- Adapter Engine -- Test Messages doesn't work.

[Former Member]

Hi !

You can send tickets by logging into the SAP Service Marketplace (service.sap.com) using a "S" type account (that is, an account username that starts with "S.....").

When sending messages via SOAP, I understand that in your SOAP client (download open source soapUI, import your wsdl, set the user and pass for authentication and execute..) you set the authentication user to some user and then you still receive PIAFUSER as the logon user...please check with another SOAP client.

Regards,

Matias.

[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