WAS v8.5 > Secure applications > Secure web services > Secure web services > Administer Web Services Security > Configure XML digital signature for v5.x web services with the dmgr console > Configure nonce using Web Services Security tokens

Configure nonce for the server level

Nonce is a randomly generated, cryptographic token used to prevent the theft of username tokens, used with SOAP messages. Nonce is used in conjunction with the basic authentication (BasicAuth) method. We can configure nonce for the server level using the WebSphere Application Server dmgr console. The information in this article supports v5.x applications only used with WAS v6.0.x and later. The information does not apply to v6.0.x and later applications.

However, you must consider the order of precedence:

  1. Application level
  2. Server level

If you configure nonce on the application level and the server level, the values specified for the application level take precedence over the values specified for the server level.

In a WAS (base) or WAS, Express environment, specify values for the Nonce cache timeout, Nonce maximum age, and Nonce clock skew fields on the server level to use nonce effectively.

To configure nonce on the server level:

  1. Connect to the dmgr console.

    Type http://localhost:port_number/ibm/console in the web browser unless we have changed the port number.

  2. Click Servers > Server Types > WebSphere application servers > server_level.

  3. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using WAS version 6.1 or earlier, click Web services: Default bindings for Web Services Security.

  4. Specify a value, in seconds, for the Nonce cache timeout field. The value specified for the Nonce cache timeout field indicates how long the nonce remains cached before it is expunged. Specify a minimum of 300 seconds. However, if we do not specify a value, the default is 600 seconds. Required for the server level.

  5. Specify (optional) a value, in seconds, for the Nonce maximum age field.

    The value specified for the Nonce Maximum Age field indicates how long the nonce is valid. Specify a minimum of 300 seconds, but the value cannot exceed the number of seconds specified for the Nonce cache timeout field on the server level.

  6. Specify a value, in seconds, for the Nonce clock skew field. The value specified for the Nonce clock skew field specifies the amount of time, in seconds, to consider when the message receiver checks the timeliness of the value. Consider the following information when we set this value:

    • Difference in time between the message sender and the message receiver if the clocks are not synchronized.
    • Time needed to encrypt and transmit the message.
    • Time needed to get through network congestion.

    Specify at least 0 seconds for the Nonce clock skew field. However, the maximum value cannot exceed the number of seconds specified in the Nonce maximum age field on the server level. If we do not specify a value, the default is 0 seconds.

  7. Restart the server. If you change the Nonce cache timeout value and do not restart the server, the change is not recognized by the server.


Related concepts:

Nonce, a randomly generated token


Related


Configure nonce for the application level


+

Search Tips   |   Advanced Search