How to call SOAP Interface Web service out of network Externaly

[former_member462539]

We have a SOAP to RFC Interface scenario in which the web service needs to be exposed to the outside of network, and should be invoked externally using dedicated user id and password for each vendor/customer. Basically we want to restrict some vendors who should not be able to access some particular services. Where do we create user id and Password for sender Communication channels? For Example, we have 10 services, where we want to give an access to 8th service for a particular vendor and that vendor should not be able to access other 9 services.

This below URL is working fine as expected, Internally, but has to work externally as well. What should be done to map externalhostname=internalhostname in the DMZ(F5 or any web dispatcher)? followed by path.

http://Internalhostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<∫erface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<∫erfaceNamespace>=name of the interface namespace

[former_member462539]

Let me put my question in different way. Let's say I have 3 separate interfaces called a,b,c using 3 different Source wsdl's and 3 Target RFC structures. For all of these 3 Interfaces a sender SOAP and Receiver RFC Communication channel is common across all 3 ICO's. Lets say we have given the url paths of all 3 interfaces details to two(x,y)/all vendors. after some time, business wants to restrict interface b access to vendor x. how it can be achieved? using Logon credentials authentication.

[Ryan-Crosby]

Yes, if you use designate logins for each vendor/customer then the authorization of each interface on the back-end can be restricted using the normal SAP authorization concept.

[former_member462539]

Would you please explain a bit more in detail on how to enable this principal propagation for Sender SOAP Channel to be invoked outside externally?

[Ryan-Crosby]

Hi,

Based on what you have described it sounds to me like you could implement principal propagation to handle the user level access per customer/vendor. As far as authorization execution for each interface you could handle that at the back-end but it's hard to say without knowing more about how the content is organized.

Regards,

Ryan Crosby