7.11. Authentication Providers§
Authentication Providers are used by Ports to authenticate connections.
See Section 8.1, “Authentication Providers”
7.11.1. Types§
The following authentication providers are supported:
Anonymous: allows anonymous connections to the Broker
External: delegates to external mechanisms such as SSL Client Certificate Authentication
Kerberos: uses Kerberos to authenticate connections via GSS-API.
SimpleLDAP: authenticate users against an LDAP server.
OAuth2: authenticate users against a OAuth2 Authorization Server.
ScramSha: authenticate users against credentials stored in a local database
Plain: authenticate users against credentials stored in a local database.
PlainPasswordFile: authenticate users against credentials stored in plain text in a local file.
MD5: authenticate users against credentials stored in a local database.
Base64MD5PasswordFile: authenticate users against credentials stored encoded in a local file.
The last five providers offer user management facilities too, that is, users can be created, deleted and passwords reset.
7.11.3. Children§
None
7.11.4. Lifecycle§
Not supported
Important
When updating an existing authentication provider, changes become effective until the Broker is restarted.
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners