Yesterday, Microsoft announced the Visual Studio Team System, a comprehensive team development platform that will include Whitehorse, FxCop, EIF, etc.
A very important component is that Microsoft finally will release a ClearCase killer (one hopes) code named Hatteras.
Eric Sink reports that this is from-the-ground-up technology that uses SQL Server as the backing store.
Here's the overview and the all-important graphic.
It appears to have it all, but at what cost?
Here's the eweek spread.
Our old friend Korby has the goods.
Update: Someone (Sir/Madam, please identify yourself) has pointed us in the right direction: WS-Federation is part of Web Services Security (WSS) -- at least that's what the document says. The WS-Federation Passive Requester Profile (PRP) is our baby. That would make my answer below incorrect!
An interesting article at news.com says that Microsoft will be pitting WS-Security standards against Liberty Alliance in replacement or augmentation of their Passport technology. In my investigation on WSE and WS-Security, Federated Identity never hit me over the head. WS-Addressing certainly allows routing, however the intermediaries do not share the security token of the end points and, thus cannot participate in the identity. Does anybody have more information on how federation should be supported with WS-Security?
The commentary here, of course, is that if WS-Security has mobile identity/single sign-on built in, there's a good chance it will sweep the other technologies away. I am confident, at least, that WS-Security will become standard for traditional sign-on. One wonders if Microsoft and IBM are really together in extending it's use into “The Federation”.
AnswerWrong: WS-Trust. I didn't need it for my investigation and didn't give it enough cycles for “burn in”. I would say, Yes, all the WS-I team is on board. Does anyone know of any specific mention of “Federation”?