A sample scenario
This document describes a usage scenario for Web services security.
In scenario 1, Client 1 invokes Web services 1. Then Web services 1 calls EJB file 2. EJB file 2 calls Web services 3 and Web services 3 calls Web services 4.
Web services security complements the WebSphere Application Server security run time and the J2EE role-based security. This scenario demonstrates how to propagate security tokens across multiple resources such as Web services and EJB files.
Related concepts
Web services security specification-a chronology
Web services security and Java 2 Platform, Enterprise Edition security
relationship
Web services security model in WebSphere Application Server
Security token
Configurations
Related tasks
Configuring the client for LTPA token authentication: specifying LTPA
token authentication
Configuring the client for LTPA token authentication: collecting the
authentication method information
Configuring the server to handle LTPA token authentication information
Configuring the server to validate LTPA token authentication information
Configuring the client security bindings using an assembly tool
Configuring the security bindings on a server acting as a client using
the administrative console
Configuring pluggable tokens using an assembly tool
Configuring pluggable tokens using the administrative console
Securing Web services for version 5.x applications based on WS-Security
Related reference
Web services security support