Chapter 11. Security

In this chapter, we will cover the following recipes:

  • Encrypting configuration properties
  • Digitally signing and verifying messages
  • Encrypting and decrypting a message
  • Encrypting all or parts of an XML message
  • Authentication and authorization using Spring Security

Introduction

In this chapter we will take an in-depth look at adding a level of security to your routing logic through a number of security-related Camel components. We will focus on making it difficult for an unauthorized party to gain access to sensitive information while messages are in-flight, to manipulate sensitive payloads, and to trigger operations to which that party is not authorized.

Beyond the topics discussed in this chapter, in order to secure your integrations you will also need to consider factors such as:

  • Restricting access to the operating system on which the application runs.
  • Password protecting JMX access so that an unauthorized party cannot change the route at runtime to wiretap or log message contents.
  • Not storing passwords or keys in plain text on the filesystem.
  • Locking down the transport mechanism. For example, applying SSL to message broker connections, or WS-Security and WS-SecurityPolicy with SOAP-based web services.

Security, after all, is a process that is broader than how a single application protects itself.

A number of Camel architectural concepts are used throughout this chapter. There is a broader overview of Camel concepts in the Preface. Full details can be found on the Apache Camel website at http://camel.apache.org.

The code for this chapter is contained within the camel-cookbook-security module of the examples.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.21.12.140