What do these specific November CTP updates and changes mean for developers building applications for Service Bus and Access Control? How are the changes significant?
Based on the fact that REST web services have become increasingly popular with both web and enterprise developers, we received feedback from the community that the lack of controlling access to REST web services is one of the major pain points faced by service developers today. As interoperability remains a goal of ours, this means that we will simplify the approach to ACS so that access control scenarios integrate well with REST. The approach is also designed to continue to appeal to all developers that want an easy way to take advantage of Service Bus and Access Control or use these services from non-Microsoft platforms. Meanwhile, we remain committed to our ongoing goals of enabling SSO and authorization for websites, supporting WS-*, and federating with a greater variety of web and enterprise identity providers, in a future release.
Related Questions
- What do these specific November CTP updates and changes mean for developers building applications for Service Bus and Access Control? How are the changes significant?
- When we make changes to our applications, do we code using the EXEC CICS statements, or in NeoKicks service calls?
- How will the November CTP release of Service Bus and Access Control benefit customer/developers?
