Configure message-level security for JAX-RPC at the application level
Modify the application-level configurations in the administrative console.
Subtopics
- Configure generator signing using JAX-RPC to protect message integrity
We can configure the generator key and signing information at the server or cell and application level to protect message integrity.- Configure consumer signing using JAX-RPC to protect message integrity
We can configure protect message integrity by configuring signing and key information at the server or cell and application level.- Configure the key information using JAX-RPC for the generator binding on the application level
The key information specifies 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.- Configure the key information using JAX-RPC for the consumer binding on the application level
We can configure the key information for the request consumer (server side) and the response consumer (client side) bindings at the application level.- Configure token generators using JAX-RPC to protect message authenticity at the application level
When we specify the token generators at the application level, the information is used on the generator side to generate the security token.- Configure token consumers using JAX-RPC to protect message authenticity at the application level
We can specify the token consumer on the application level. The token consumer information is used on the consumer side to incorporate the security token.- Configure encryption using JAX-RPC to protect message confidentiality at the application level
We 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.- Configure encryption to protect message confidentiality at the application level
We can configure the encryption information for the request consumer (server side) and response consumer (client side) bindings at the application level.- Configure generator signing using JAX-RPC to protect message integrity
We can configure the generator key and signing information at the server or cell and application level to protect message integrity.- Configure consumer signing using JAX-RPC to protect message integrity
We can configure protect message integrity by configuring signing and key information at the server or cell and application level.- Configure the key information using JAX-RPC for the generator binding on the application level
The key information specifies 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.- Configure the key information using JAX-RPC for the consumer binding on the application level
We can configure the key information for the request consumer (server side) and the response consumer (client side) bindings at the application level.- Configure token generators using JAX-RPC to protect message authenticity at the application level
When we specify the token generators at the application level, the information is used on the generator side to generate the security token.- Configure token consumers using JAX-RPC to protect message authenticity at the application level
We can specify the token consumer on the application level. The token consumer information is used on the consumer side to incorporate the security token.- Configure encryption using JAX-RPC to protect message confidentiality at the application level
We 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.- Configure encryption to protect message confidentiality at the application level
We can configure the encryption information for the request consumer (server side) and response consumer (client side) bindings at the application level.