Securing Web services for v5.x applications using a pluggable token
Overview
WebSphere Application Server provides several different methods to secure your Web services; a pluggable token is one of these methods. You might secure your Web services using any of the following methods:
- XML digital signature
- XML encryption
- Basicauth authentication
- Identity assertion authentication
- Signature authentication
- Pluggable token
Complete the following steps to secure your Web services using a pluggable token:
Procedure
- Generate a security token using the Java Authentication and Authorization Service (JAAS) CallbackHandler interface. The Web services security run time uses the JAAS CallbackHandler interface as a plug-in to generate security tokens on the client side or when Web services is acting as a client.
- Configure your pluggable token. To use pluggable tokens to secure your Web services, configure both the client request sender and the server request receiver. One can configure your pluggable tokens using either the WAS administrative console or the WAS Toolkit. For more information, see the following topics:
- Configuring pluggable tokens using an assembly tool
- Configuring pluggable tokens using the administrative console
See also
Configuring pluggable tokens using an assembly tool
Configuring pluggable tokens using the administrative console
Pluggable token support
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
See Also
Lightweight Third Party Authentication