I was told that one of the differences w.r.t dealing with webservices between MB and WAS is that ... WAS supports built-in authentication whereas MB doesn't. So, we need to do round-about ways of passing user-id/pwd like in:
There are webservices standards that specify methods of authenticating the requester.
WAS implements more WS-* standards than Broker does.
Currently. As far as I know.
You haven't really identified if the .NET services are using any of these WS-* standards for security. It's entirely possible that the .NET services have been written in complete ignorance of all the standards for passing authentication, and have implemented their own solution. _________________ I am *not* the model of the modern major general.
The .NET webservice is yet to be built and that won't be done until the msgflows ( webservice clients) are built - i know it sounds very strange but that's our customer so, I won't comment on that part.
Currently the .NET team asked us what WS-security standards the broker supports so they can decide what/how to code their services.
I don't know off the top of my head what WS-* standards broker supports. I *believe* that it's only the WS-basic profile.
You should probably open a PMR to get clarification. These things change fairly quickly - especially just after the release of an FP. _________________ I am *not* the model of the modern major general.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum