Secure messages using JAX-RPC at the request and response consumers
We can secure messages at the request and response consumer level to protect message confidentiality and security.
To secure messages, we can:
- Set signing to protect message confidentiality
- Set encryption to protect message confidentiality at the server or cell level and at the application level
- Set tokens to protect message authenticity at the server or cell level and at the application level
- To configure consumer signing to protect message confidentiality, see the steps outlined in Set consumer signing using JAX-RPC to protect message integrity
- To configure encryption to protect message confidentiality at the application level, see the steps outlined in Set encryption to protect message confidentiality at the application level.
- To configure encryption to protect message confidentiality at the server or cell level, see the steps outlined in Set encryption to protect message confidentiality at the server or cell level.
- To configure tokens at the application level to protect message authenticity, see the steps outlined in Set token consumers using JAX-RPC to protect message authenticity at the application level.
- To configure tokens at the server or cell level to protect message authenticity, see the steps outlined in Set token consumers using JAX-RPC to protect message authenticity at the server or cell level.
Results
By completing the steps in the previous tasks, we have secured messages at the request and response consumer level.
Set consumer signing using JAX-RPC to protect message integrity
Set encryption to protect message confidentiality at the application level
Set encryption to protect message confidentiality at the server or cell level
Set token consumers using JAX-RPC to protect message authenticity at the application level
Set token consumers using JAX-RPC to protect message authenticity at the server or cell level
Related tasks
Secure JAX-RPC Web services using message level security