In designing the security for your enterprise application with multiple Web services, you don’t want that each of the services handle user authentication by itself. Then which of the following you can use in your design?
A.
enable secure conversation for each service
B.
a centralized Policy Decision Point (PDP) via XACML
C.
a Security Token Service (STS)
D.
use transport level security with SSL
A security token service (STS) is a software based identity provider responsible for issuing security tokens as part of a claims-based identity system.[1]
In a typical usage scenario, a client requests access to a secure software application, often called a relying party. Instead of the application authenticating the client, the client is redirected to an STS. The STS authenticates the client and issues a security token. Finally, the client is redirected back to the relying party where it presents the security token. The token is the data record in which claims are packed, and is protected from manipulation with strong cryptography. The software application verifies that the token originated from an STS trusted by it, and then makes authorization decisions accordingly. The token is creating a chain of trust between the STS and the software application consuming the claims. This process is illustrated in the Security Assertion Markup Language (SAML) use case, demonstrating how single sign-on can be used to access web services.
Security token services can be offered as web services, through the use of application programming interfaces (APIs), or for native applications in conjunction with software development kits (SDKs).[2]