Skip to Content

SOAP Receiver Connecting as Guest despite configured credentials

I have a SOAP receiver connected to our SAP system with Authentication Data provided:

I am using this SOAP Receiver in 2 ICOs. The first ICO has a SOAP Sender and uses "Propagate Principal" - this ICO works. In the second ICO, the sender is file based, so no credentials are available for propagation. For this reason default credentials are configured in the Receiver channel as noted above. However, this ICO does not work - the Receiver is attempting to connect as "Guest" and getting a Not Authorized error.

Any suggestions?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 20, 2017 at 04:23 AM

    Hi Alex,

    Can you try pasting the target url in a browser and then enter the credentials there?

    It is also possible that the user is already locked. Aside from that, are you using dynamic configuration? If yes, then the credentials need to be maintained via TAuthKey.



    Add comment
    10|10000 characters needed characters exceeded

    • Correct. In our SOAP in / SOAP out ICO, we are using principal propagation successfully. The userid we supply from a test client such as SOAP UI is what is used when connect from PI to ECC.

      In our File in / SOAP out ICO, the receiver uses the userid "Guest". It does this with either the same receiver as the SOAP-SOAP ICO, or if I create a new SOAP Receiver. In both cases the receiver is configured with valid credentials.

      By the way, that TraceHTTP is a useful feature - thanks! (Although I have not yet resolved our issue)

  • Oct 23, 2017 at 08:23 PM

    Sigh. So the "Guest" in the logs was a red herring. Turns out the system account I was supplied ended up being locked. In trying different tests I guess I thought I had used my personal account for the file test, but maybe had not. After rebuilding the Receiver channel from scratch and using my account, it worked - but the logs still showed "Guest". At that point I double checked the system account and spotted that it was locked.

    It is now working.

    Add comment
    10|10000 characters needed characters exceeded