Task Based UI @ Siebel 7.8 | Next Tip »Home

Implementing Secure Outbound Web Services

OkAvarageGoodVery GoodExcellent (1 votes, average: 5.00 out of 5)
Loading ... Loading ...
  • Share/Bookmark

Related Posts


Article by neel

Authors bio is coming up shortly. neel tagged this post with: Read 387 articles by neel
  • Binesh
    babu, this is awesome. I was waiting for this for a very long time. One more thing I noticed is that, even though these credentials are updated in the WSDLS, we will not be able to see this. Try to use the WSDL given by the external system in SOAP Ui, . In the properties window you can see that the username and passowrd are copied and in the first run itself you will get the soap response. If the same WSDLs is moved to Siebel Tools, you will be getting an authentication error from the target middleware/system. Your suggestion is the solution for this problem. Meanwhile most of the middleware systems have a capability to limit the IP addresses from which the request is coming.In a small organisation, people are using network security rather than web service security. Middleware can also do an anonymous registration based on IP addressess. I dont have an example to figure this right here.
blog comments powered by Disqus

Polls

Do you like the new Comment System and new look to Site?

View Results

Loading ... Loading ...