Chapter 9. Securing Mule
In this chapter
- Securing Mule with Spring Security
- Using JAAS with Mule
- Using security filters to secure endpoints
Security is a challenge in application development and deployment—a challenge that’s exacerbated by application integration. Single sign-on technologies such as Kerberos, CAS, and LDAP minimize these burdens, but it’s unlikely that every application in your environment supports the SSO technology at hand. Even if this is the case, all bets are off when you’re integrating with applications outside of your company’s data centers. Thankfully, Mule employs the same architectural principles we saw in part 1 in its handling of security. This gives you the opportunity to decouple your security concerns from your routing, transformation, and components.
You’ll see in this chapter how Mule’s security architecture will enable you to quickly simplify what would otherwise be complex security tasks. These simplifications will cross-cut your authentication, authorization, and encryption concerns. We’ll see how Clood, Inc., uses Mule’s security features to perform authentication on endpoints, authorize users, and encrypt payloads. We’ll also demonstrate how Mule enables you to pull this all together to intelligently and quickly secure your integration infrastructure.