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
Distribute nonce caching to servers in a cluster
Distributed nonce caching enables you to distribute the cache for a nonce to different servers in a cluster.
Before configuring distributed nonce caching, configure cache replication.
For more information, read about configuring cache replication.
When you configure the cache replication, do not use the default value of a single replica for the Number of replicas for dynamic cache replication domains. Instead, use a full group replica for any replication domains that you configure for dynamic cache. If you cannot select the option, verify your cache replication configuration.
In previous releases of WAS, the nonce was cached locally.
To use this feature, complete the following actions:
Procedure
- Verify that you created an appropriate domain setting when you form a cluster.
For more information, read about creating clusters.
- Verify that replication domain is properly secured. The nonce cache is crucial to the integrity of the nonce validation process. If the nonce cache is compromised, then you cannot trust the result of the validation process.
- In the admin console for the cell level, set the Distribute nonce caching option by enabling the distributed cache option in the Security cache panel. We can enable the option...
- Click Services > Security cache
- Click the check box to select the Enable distributed caching option.
- Verify that the dynamic cache service is enabled for each one of the application servers in your cluster. To access the dynamic cache service through the admin console...
- Click Servers > Server Types > WebSphere application servers > server_name
.
- Under Container settings, click Container services > Dynamic cache service.
- Confirm that the Enable service at server startup option is selected.
- In the admin console for the server level, select the Distribute nonce caching option. We can enable the option...
- Click Security > Web services.
- Select the Distribute nonce caching option.
- Restart the servers within your cluster.
Results
When you select the Distribute nonce caching option in the admin console, the nonce is propagated to other servers in the environment. However, the nonce might be subject to a one-second delay in propagation and subject to any network congestion.
What to do next
For more information on distributed nonce caching, see Web Services Security enhancements.
Nonce, a randomly generated token
Web Services Security enhancements
Distributed nonce cache
Configure Web Services Security using JAX-RPC at the platform level
Related
Security considerations for web services