Using basic authentication in SAP PI calls from .NET

Question

I'm getting the error message below when trying to call the SAP PI Web Services using C#.net console app:

The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Basic realm="XISOAPApps"'.m="XISOAPApps"'.

My custombinding looks like this:

<customBinding>  
        <binding name="CustomHttpTransportBinding">  
          <textMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16"  
              messageVersion="Soap11" writeEncoding="utf-8">  
            <readerQuotas maxDepth="10000000" maxStringContentLength="10000000"  
                maxArrayLength="67108864" maxBytesPerRead="65536" maxNameTableCharCount="100000" />  
          </textMessageEncoding>  
          <httpTransport authenticationScheme="Basic" bypassProxyOnLocal="false"  
              hostNameComparisonMode="StrongWildcard" keepAliveEnabled="false"  
              proxyAuthenticationScheme="Basic" realm="XISOAPApps" useDefaultWebProxy="true" />  
        </binding>  
      </customBinding>

Could anyone please correct me if I'm doing something wrong above? Thank you.

Did you add the user name and password for the system on the proxy? — Richard Blewett, Jun 25 '11 at 16:06
Yep, proxy.Credentials.Username="anyuser"; proxy.Credentials.Password="good". — Nil Pun, Jun 25 '11 at 22:22
I'd suggest using message logging on the client or fiddler to see what your request looks like on the wire and see if anything looks out of place — Richard Blewett, Jun 26 '11 at 07:38

score 9 · Answer 1 · answered Feb 14 '13 at 22:15

9

SAP PI webservice with Basic Authentication:

      <basicHttpBinding>
        <binding ...>
          <security mode="TransportCredentialOnly">
            <transport clientCredentialType="Basic" />
          </security>
        </binding>
      </basicHttpBinding>

answered Feb 14 '13 at 22:15

Brian Low

11,605
4
58
63

Thanks John, unforetunately, svcutil still outputs the same warning even with the updated namespace. – Brian Low Mar 11 '13 at 20:22

score 0 · Answer 2 · answered Apr 22 '16 at 16:42

Verify that your SAP web service credentials are correct, and not locked. I just came across this error, and I asked my SAP P.I. Admin to verify the SAP service credentials, and it turns out that they were locked. Everything worked fine once she unlocked the SAP credentials for me.

Using basic authentication in SAP PI calls from .NET

2 Answers2