Loading...

XML

Word

Printable

Affects:

Release Notes
Release Note Text:

Hide
Previously, the broker could not connect to an LDAP provider using Kerberos credentials. In the 7.1 version of AMQ Broker, you can enable the broker to use Kerberos by adding configuration to the login.config configuration file. See the "Security" chapter of the product documentation titled Using AMQ Broker for more information.

Show
Previously, the broker could not connect to an LDAP provider using Kerberos credentials. In the 7.1 version of AMQ Broker, you can enable the broker to use Kerberos by adding configuration to the login.config configuration file. See the "Security" chapter of the product documentation titled Using AMQ Broker for more information.
Release Note Status:
Documented as Feature Request
Target Release:

AMQ 7.1.0.GA

This avoids the need to put private credentials in login.config for the ldap jaas login module to connect to LDAP.

the credential used for the kerberos amqp acceptor can be reused and the login config scope can be configured

is blocked by

ENTMQBR-948 GSSAPI IBM JDK - clients get authentication refused first time they connect to broker

relates to

AMQDOC-2210 REQ: Document " Implement a Kerberos Authentication Mechanism between clients and the broker"

AMQDOC-2674 REQ: Document LDAP role mapping of kerberos authenticated users

ENTMQBR-789 Add support for Ldap role mapping of kerberos authenticated users