Implementing Message Layer Security with a Security Token Service (STS) in WSE 3.0
| Retired Content |
|---|
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Implementing Message Layer Security with a Security Token Service (STS) in WSE 3.0
Web Service Security: Scenarios, Patterns, and Implementation Guidance for Web Services Enhancements (WSE) 3.0Microsoft Corporation
patterns & practices Developer Center
Web Service Security: Home
December 2005
| Download | Download this guide in PDF format |
| Community | Web Service Security Community Workspace [Content link no longer available, original URL:http://go.microsoft.com/fwlink/?LinkId=57044] |
Note This pattern is currently under development. It is due for release in early 2006.
Context
You are implementing brokered authentication in an application deployed on computers running Windows operating system software with security implemented at the message layer. Web services need to authenticate clients in a heterogeneous environment so that you can implement additional controls, such as authorization and auditing. The authentication broker negotiates trust between client applications and Web services, which removes the need for a direct relationship. The authentication broker should issue signed security tokens for authentication.
Implementation Strategy
A QuickStart that demonstrates how to develop a Web Service Enhancements (WSE) 3.0 Security Token Service (STS) that issues XML tokens is currently under development. This pattern will be updated when the QuickStart is released.
If you are interested in obtaining a Community Technical Preview (CTP) release or would like to contribute requirements, join the Security Token Service Quickstart community workspace [Content link no longer available, original URL:http://go.microsoft.com/fwlink/?LinkId=57069].
| Retired Content |
|---|
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
