Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.4.2. Broker JAAS Authentication
Overview Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
The Java Authentication and Authorization Service (JAAS) provides a general framework for implementing authentication and authorization in Java applications. In the context of Apache ActiveMQ, the main purpose of JAAS is to implement authentication of JMS credentials (which consist of a username and a password). In contrast to SSL/TLS security, which is mainly used to verify a broker's identity, the JAAS authentication mechanism verifies client identities.
For more background information about the JAAS framework, see the JAAS Reference Guide.
JAAS realms Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
A JAAS realm is essentially an instance of a login module that provides access to a repository of authentication data. Different JAAS realms provide access to different repositories of authentication data and might perform authentication in different ways.
Standalone applications typically define a JAAS realm by creating an entry in a JAAS login configuration file. Applications deployed in the OSGi container, on the other hand, must define a JAAS realm using a special Apache Karaf schema in a blueprint file (as described in Section 2.1.2, “Defining JAAS Realms”).
How to define JAAS realms Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
If you need to define your own JAAS realm for an application deployed in the OSGi container, you must use the Apache Karaf JAAS schema,
http://karaf.apache.org/xmlns/jaas/v1.0.0
. For details, see Section 2.1, “JAAS Authentication”.
The karaf realm Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
The OSGi container has a predefined JAAS realm, the
karaf
realm, which you can also use in your applications See Section 1.1, “OSGi Container Security”.
Configuring JAAS authentication for JMS credentials Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
To authenticate JMS credentials, use Red Hat JBoss A-MQ's
jaasAuthenticationPlugin
plug-in, which can be configured as follows:
The
jaasAuthenticationPlugin
plug-in is intended for use with any kind of username/password credentials and can be used in combination with the pre-defined karaf
realm or with a realm defined using the LDAP login module.
Configuring JAAS authentication for X.509 certificates Copy linkLink copied to clipboard!
Copy linkLink copied to clipboard!
If the broker uses SSL/TLS, you could also authenticate the received client certificate using Red Hat JBoss A-MQ's
jaasCertificateAuthenticationPlugin
plug-in, which can be configured as follows:
The
jaasCertificateAuthenticationPlugin
plug-in is only intended for use with X.509 certificate credentials and must be used in combination with a realm defined using the TextFileCertificateLoginModule
login module. For more details, see the Security Guide from the JBoss A-MQ library.