summaryrefslogtreecommitdiff
path: root/qpid/doc/book/src/java-broker/Java-Broker-Concepts-Authentication-Providers.xml
blob: dd7c291c77f3e0040a2e42b9e003a2547a5fd784 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<?xml version="1.0" encoding="utf-8"?>
<!--

 Licensed to the Apache Software Foundation (ASF) under one
 or more contributor license agreements.  See the NOTICE file
 distributed with this work for additional information
 regarding copyright ownership.  The ASF licenses this file
 to you under the Apache License, Version 2.0 (the
 "License"); you may not use this file except in compliance
 with the License.  You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing,
 software distributed under the License is distributed on an
 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
 under the License.

-->

<section id="Java-Broker-Concepts-Authentication-Providers">
    <title>Authentication Providers</title>
    <para>
        <emphasis>Authentication Providers</emphasis> are used to authenticate connections to <emphasis>Ports</emphasis>.
        Many <emphasis>Authentication Providers</emphasis> can be configured on the Broker at the same time, from which
        each <emphasis>Port</emphasis> can be assigned one.
    </para>
    <para>
        The following authentication providers are supported:
        <itemizedlist>
            <listitem><para><link linkend= "Java-Broker-Security-Anonymous-Provider">Anonymous</link>:
            allows anonymous connections to the broker</para></listitem>
            <listitem><para><link linkend= "Java-Broker-Security-External-Provider">External</link>:
            delegates to external mechanisms such as SSL Client Certificate Authentication</para></listitem>
            <listitem><para><link linkend= "Java-Broker-Security-Kerberos-Provider">Kerberos</link>:
            uses Kerberos to authenticate connections via GSS-API.</para></listitem>
            <listitem><para><link linkend= "Java-Broker-Security-LDAP-Provider">SimpleLDAP</link>:
            authenticate users against an LDAP server.</para></listitem>
            <listitem><para><link linkend= "Java-Broker-Security-PlainPasswordFile-Provider">PlainPasswordFile</link>:
            authenticate users against credentials stored in plain text in a local file.</para></listitem>
            <listitem><para><link linkend= "Java-Broker-Security-Base64MD5PasswordFile-Provider">Base64MD5PasswordFile</link>:
            authenticate users against credentials stored encoded in a local file.</para></listitem>
        </itemizedlist>
    </para>
    <para>
        The Password File based providers can perform explicit management (adding, removing, changing passwords)
        of users via the Brokers management interfaces. The other providers offer no ability to manage users as they either have no scope
        for user management (e.g Anonymous) or delegate this task to other systems (e.g LDAP).
    </para>
    <para>The configuration details for Authentication Providers are covered in <xref linkend= "Java-Broker-Security-Authentication-Providers"/>.</para>
</section>