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.
To protect message integrity, we can:
- Configure the signing information for the consumer binding on the application level or at the server or cell level
- Configure the key information for the consumer binding on the application level or at the server or cell level
- To configure the signing information for the consumer binding on the application level, see the steps outlined in Configure the signing information using JAX-RPC for the consumer binding on the application level
- To configure the signing information for the consumer binding on the server or cell level, see the steps outlined in Configure the signing information using JAX-RPC for the consumer binding on the server or cell level
- To configure the key information for the consumer binding on the application level, see the steps outlined in Configure the key information for the consumer binding on the application level
- To configure the key information for the consumer binding on the server or cell level, see the steps outlined in Configure the key information for the consumer binding using JAX-RPC on the server or cell level
Results
By completing the steps in these tasks, we have configured the consumer signing to protect the integrity of messages.
Subtopics
- Configure the signing information using JAX-RPC for the consumer binding on the application level
We can configure the signing information for the server-side request consumer and the client-side response consumer bindings at the application level.
Related tasks
Secure messages using JAX-RPC at the request and response generators Configure encryption using JAX-RPC to protect message confidentiality at the server or cell level Configure token generators using JAX-RPC to protect message authenticity at the application level Secure messages using JAX-RPC at the request and response consumers