cancel
Showing results for 
Search instead for 
Did you mean: 

Troubleshooting Webservices

Former Member
0 Kudos

Hi,

So, I'm in the midst of troubleshooting a 3rd party tool, that connects to sap me via web services. And I throws me an error I just can't figure out.

this is the error:

System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Basic realm="/manufacturing-services/ProductionServiceService"'.

---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.

at System.Net.HttpWebRequest.GetResponse()

at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

--- End of inner exception stack trace ---

I have tested all the webservices with SOAPUI and they work correctly.

Where is this basic scheme and where can I change the scheme so it auths correctly?`

regards,

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

All ME web services use basic http authentication and schema Basic is hardcoded and cannot be changed at runtime.

Few things to check:

- your client software provides valid username/password for each request, including wsdl retrieval (if applicable);

- specified user has SAP_ME_INTEGRATOR role.

Former Member
0 Kudos

Hi!

this is from the developer of the tool:

I've been testing the tool using MesLogin/Password (Kari/Happo1) and with those it works just fine.

When I switched to same login that you used (XML/password) the SAP allows complete messages to be send but raises "unauthorized access" error when trying to send start or assemble messages.

I have absolutely no idea on how SAP user authentication is configured, so hopefully someone else can advise on how to proceed with this.

regards,

Tarvi.

Former Member
0 Kudos

Hi,

ME doesn't have separate authorization concepts for complete and start messages.

What version of ME are you using? In 5.2 it's possible to use Single-Service Administration (from NWA) to setup basic http authentication. In 6.0.1 we set the default basic http authentication for all web services and this is done throught web.xml security constraint.

Can you simulate web service calls with SoapUI to troubleshoot security?

Thanks,

Bakhtiyar

Former Member
0 Kudos

Hi,

Yes, debuged the connections with soapUI. used a custom made user to test it and it worked. As the programmer pointed out the problems seems to be with the built-in XML user. For some reason, it times out the authentication. Everything seems to work fine with custom made administrator users.

Now the question is. how to i troubleshoot the XML user auth rights in the SAP ME 5.2 system. To check that everything is as it should be.

regards,