I’ve created a custom SOAP-MSG listener which has a custom Execute ACL, named “SOAP_Processor”. I have created a user, “LVKUser”, which is a part of this ACL. Calling SOAP-MSG webservices through this listener, authenticating with user “LVKUser”, works fine when calling from clients such as .NET and SOAPStation (SOAPStation used as a proxy webservice manager).
But I ran into a problem yesterday when trying to use webMethods itself to call these services. I use the Web Service Connector to create a client flow. When running the flow, setting user as “LVKUser” I get the following exception: [ISC.0064.9314] Authorization Required: [ISS.0084.9004] Access Denied.
When looking at the Session log the User ID is always “Default”.
If I use SOAPStation as a proxy between, everything works fine. Looking at the Session log after connecting with SOAPStation I see User ID “Default” and after that on the same second, User ID “LVKUser”.
Is this a bug in flow pub.client:http? It seems to me that it doesn’t send the username and password in this case.
When I do the same with a custom RPC webservice listener, everything works fine using client flow pub.client:soapRPC.
The webMethods server is version 6.1 with the following updates:
Java VersionwriteTD(“rowdata-l”); 1.4.2 (48.0)
I’ve tried this on two other webMethods servers with the same result.