Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Secure web services > Secure web services > Administer Web Services Security > Administer message-level security for JAX-RPC web services
Configure Web Services Security using JAX-RPC at the platform level
In the platform configuration, general properties and additional properties can be specified, and the default binding is included. We can configure security for web services at a platform level with a variety of tasks including configuring key locators, trust anchors, and the collection certificate at the generator, consumer binding, and sever levels.
IBM WAS supports the JAX-WS programming model and JAX-RPC. JAX-WS is the next generation web services programming model extending the foundation provided by JAX-RPC. Using the strategic JAX-WS programming model, development of web services and clients is simplified through support of a standards-based annotations model. Although JAX-RPC and applications are still supported, take advantage of the easy-to-implement JAX-WS programming model to develop new web services applications and clients. bprac
Besides the application-level constraints, there is a cell-level and server-level Web Services Security (WSS) configuration called a platform-level configuration:
- These configurations are global for all applications and include some configurations only for WAS v5.x applications and some only for version 6.0.x applications.
- We can use the default binding as an application-level binding configuration so that applications do not have to define the binding in the application. There is only one set of default bindings that can be shared by multiple applications. This set is only available for WAS Version 6.x applications.
Therefore, binding configuration files can be specified at these levels: application, server, and cell. Each binding configuration overrides the next higher one. For any deployed application, the nearest configuration binding is applied. The visibility scope of the binding depends on where the file is located. If the binding is defined in an application, its visibility is scoped to that particular application. If it is located at the server level, the visibility scope is all applications that are deployed on that server. For WAS ND, if it is located at the cell level, the visibility scope is all applications deployed on all servers of the cell.
To ensure Web Services Security at the platform level, you can configure:
- A nonce on the server or cell level
- The key locator for the generator or consumer binding on the application level, server level, or cell level
- Trust anchors for the generator or consumer binding on the application level, server level, or cell level
- The collection certificate store for the generator or consumer binding on the application level, server level or cell level
- Trusted ID evaluators on the server or cell level
- Hardware cryptographic devices for Web Services Security
- The rrdSecurity.props property file
Procedure
- To configure a nonce on the server or cell level, see the steps in Configure a nonce on the server or cell level
- To configure the key locator for the generator binding on the application level, see the steps in Configure the key locator using JAX-RPC for the generator binding on the application level
- To configure the key locator for the consumer binding on the application level, see the steps in Configure the key locator using JAX-RPC for the consumer binding on the application level
- To configure the key locator on the server or cell level, see the steps in Configure the key locator using JAX-RPC on the server or cell level
- To configure trust anchors for the generator binding on the application level, see the steps in Configure trust anchors for the generator binding on the application level
- To configure trust anchors for the consumer binding on the application level, see the steps in Configure trust anchors for the consumer binding on the application level
- To configure trust anchors on the server or cell level, see the steps in Configure trust anchors on the server or cell level
- To configure the collection certificate store for the generator binding on the application level, see the steps in Configure the collection certificate store for the generator binding on the application level
- To configure the collection certificate store for the consumer binding on the application level, see the steps in Configure the collection certificate store for the consumer binding on the application level
- To configure the collection certificate on the server or cell level, see the steps in Configure the collection certificate on the server or cell level
- To configure trusted ID evaluators on the server or cell level, see the steps in Configure trusted ID evaluators on the server or cell level
- To enable hardware cryptographic devices for Web Services Security, see the steps in Enable hardware cryptographic devices for Web Services Security
- To work with the rrdSecurity.props file, see rrdSecurity.props file
Results
By completing these steps, we have configured Web Services Security at the platform level.
Related
Configure a nonce on the server or cell level
Distribute nonce caching to servers in a cluster
Configure the key locator using JAX-RPC for the generator binding on the application level
Configure the key locator using JAX-RPC for the consumer binding on the application level
Configure the key locator using JAX-RPC on the server or cell level
Configure trust anchors for the generator binding on the application level
Configure trust anchors for the consumer binding on the application level
Configure trust anchors on the server or cell level
Configure the collection certificate store for the generator binding on the application level
Configure the collection certificate store for the consumer binding on the application level
Configure the collection certificate on the server or cell level
Configure trusted ID evaluators on the server or cell level
rrdSecurity.props file
Secure JAX-RPC web services using message-level security