Configuring message-level security for JAX-RPC at the server or cell level

Specify the server-level or cell-level configuration.

Subtopics

• Configure the signing information using JAX-RPC for the generator binding on the server or cell level
  We can configure the signing information for the client-side request generator and the server-side response generator bindings at the server or cell level.

• Configure the signing information using JAX-RPC for the consumer binding on the server or cell level
  We can configure the signing information for the client-side request generator and server-side response generator bindings at the server or cell level.

• Configure the key information for the generator binding using JAX-RPC on the server or cell level
  Use the key information for the default generator to specify the key used by the signing or the encryption information configurations if these bindings are not defined at the application level.

• Configure the key information for the consumer binding using JAX-RPC on the server or cell level
  The key information for the default consumer is used to specify the key for the signing or the encryption information configurations if these bindings are not defined at the application level.

• Configure encryption using JAX-RPC to protect message confidentiality at the server or cell level
  We can configure the encryption information for the generator binding on the server or cell level.

• Configure encryption to protect message confidentiality at the server or cell level
  The encryption information for the default consumer specifies how to process the encryption information on the receiver side if these bindings are not defined at the application level. WebSphere Application Server provides default values for the bindings. However, an administrator must modify the defaults for a production environment.

• Configure token generators using JAX-RPC to protect message authenticity at the server or cell level
  The token generator on the server or cell level is used to specify the information for the token generator if these bindings are not defined at the application level. The signing information and the encryption information can share the token generator information, which is why they are all defined at the same level.

• Configure token consumers using JAX-RPC to protect message authenticity at the server or cell level
  The token consumer on the server or cell level is used to specify the information needed to process the security token if it is not defined at the application level.