Configuring message-level security for JAX-RPC at the application level
Modify the application-level configurations in the administrative console.
Subtopics
Configuring generator signing using JAX-RPC to protect message integrity
You can configure the generator key and signing information at the server or cell and application level to protect message integrity.Configuring consumer signing using JAX-RPC to protect message integrity
You can configure protect message integrity by configuring signing and key information at the server or cell and application level.Configuring the key information using JAX-RPC for the generator binding on the application level
The key information is used to specify the configuration needed to generate the key for digital signature and encryption. The signing information and the encryption information configurations can share the key information, so they are both defined at the same level.Configuring the key information using JAX-RPC for the consumer binding on the application level
You can configure the key information for the request consumer (server side) and the response consumer (client side) bindings at the application level.Configuring token generators using JAX-RPC to protect message authenticity at the application level
When you specify the token generators at the application level, the information is used on the generator side to generate the security token.Configuring token consumers using JAX-RPC to protect message authenticity at the application level
You can specify the token consumer on the application level. The token consumer information is used on the consumer side to incorporate the security token.Configuring encryption using JAX-RPC to protect message confidentiality at the application level
You can configure encryption information, used to specify how the generators (senders) encrypt outgoing messages, for the request generator (client side) and the response generator (server side) bindings at the application level.Configuring encryption to protect message confidentiality at the application level
You can configure the encryption information for the request consumer (server side) and response consumer (client side) bindings at the application level.Configuring generator signing using JAX-RPC to protect message integrity
You can configure the generator key and signing information at the server or cell and application level to protect message integrity.Configuring consumer signing using JAX-RPC to protect message integrity
You can configure protect message integrity by configuring signing and key information at the server or cell and application level.Configuring the key information using JAX-RPC for the generator binding on the application level
The key information is used to specify the configuration needed to generate the key for digital signature and encryption. The signing information and the encryption information configurations can share the key information, so they are both defined at the same level.Configuring the key information using JAX-RPC for the consumer binding on the application level
You can configure the key information for the request consumer (server side) and the response consumer (client side) bindings at the application level.Configuring token generators using JAX-RPC to protect message authenticity at the application level
When you specify the token generators at the application level, the information is used on the generator side to generate the security token.Configuring token consumers using JAX-RPC to protect message authenticity at the application level
You can specify the token consumer on the application level. The token consumer information is used on the consumer side to incorporate the security token.Configuring encryption using JAX-RPC to protect message confidentiality at the application level
You can configure encryption information, used to specify how the generators (senders) encrypt outgoing messages, for the request generator (client side) and the response generator (server side) bindings at the application level.Configuring encryption to protect message confidentiality at the application level
You can configure the encryption information for the request consumer (server side) and response consumer (client side) bindings at the application level.


File name: twbs_securerpc_app_level.html