qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Farrellee (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Updated: (QPID-648) Provide some form of authentication
Date Fri, 09 May 2008 16:50:55 GMT

     [ https://issues.apache.org/jira/browse/QPID-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matthew Farrellee updated QPID-648:

    Attachment: SASLConfigPackage.diff

Initial packaging of SASL config and default database

Moved make rules for etc/ into new etc/Makefile.am, and added sasl2/qpidd.conf. Updated qpidc.spec.in
to package new SASL files, and require cyrus-sasl[-devel] for qpidd.

The default sasl2/qpidd.conf allows for ANONYMOUS and PLAIN authentication, and the default
sasldb contains a single user, guest, with an obvious password.

Also, added an --auth-realm option to qpidd so that the broker knows what realm to look for
the authenticating users in. The default realm is QPID. So, either users should be added to
that realm in the sasldb file or --auth-realm should be used to specify the desired realm.

It is important to note that to use any default clients (qpid tools/console/etc) right now
there must be a guest user in the realm that the broker is using. The default sasldb contains
the guest@QPID user.

> Provide some form of authentication
> -----------------------------------
>                 Key: QPID-648
>                 URL: https://issues.apache.org/jira/browse/QPID-648
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>            Assignee: Gordon Sim
>            Priority: Minor
>         Attachments: sasl_authentication.patch2, sasl_final.patch, sasl_listmech.patch,
sasl_plain_auth.patch, SASLConfigPackage.diff
> It is required by JMS to authenticate users at connection creation time. It would be
useful if the broker can provide such a basic authentication mechanism. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message