Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 54706 invoked from network); 29 Apr 2009 02:45:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Apr 2009 02:45:38 -0000 Received: (qmail 36225 invoked by uid 500); 29 Apr 2009 02:45:38 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 36159 invoked by uid 500); 29 Apr 2009 02:45:38 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 36149 invoked by uid 99); 29 Apr 2009 02:45:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Apr 2009 02:45:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [38.98.186.144] (HELO smtp-out.01.com) (38.98.186.144) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Apr 2009 02:45:28 +0000 Received: from asav-2.01.com (localhost.localdomain [127.0.0.1]) by asav-2.01.com (8.13.1/8.13.1) with ESMTP id n3T2hJD5024923 for ; Tue, 28 Apr 2009 21:43:19 -0500 Received: from smtp-2.01.com (smtp-2.01.com [38.98.186.158]) by asav-2.01.com (asav-2.01.com [10.25.1.12]) envelope-from with ESMTP id l3RLhJ2831449346O8 ret-id none; Tue, 28 Apr 2009 21:43:19 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-2.01.com (Postfix) with ESMTP id 695F61AD3D8 for ; Tue, 28 Apr 2009 21:43:19 -0500 (CDT) Received: from smtp-2.01.com ([127.0.0.1]) by localhost (smtp-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ym1soNdns56y for ; Tue, 28 Apr 2009 21:43:19 -0500 (CDT) Received: from mail-3.01.com (mail-3.01.com [38.98.186.155]) by smtp-2.01.com (Postfix) with ESMTP id 4E8D01AD3CD for ; Tue, 28 Apr 2009 21:43:19 -0500 (CDT) Date: Tue, 28 Apr 2009 21:43:19 -0500 (CDT) From: Garrett Smith To: users@qpid.apache.org Message-ID: In-Reply-To: <287178095.1880391240972565007.JavaMail.root@mail-3.01.com> Subject: Authentication woes - C++ broker, Python client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [64.7.13.254] X-Mailer: Zimbra 5.0.13_GA_2791.RHEL5_64 (ZimbraWebClient - FF3.0 (Win)/5.0.13_GA_2791.RHEL5_64) X-smtpf-Report: client=relay,white,ipv6; mail=; rcpt= X-FSL-MailScanner-Information: Please contact postmaster@01.com for more information X-FSL-MailScanner: Found to be clean X-FSL-MailScanner-SpamCheck: X-FSL-MailScanner-From: g@rrett.us.com X-Virus-Checked: Checked by ClamAV on apache.org I'm running into this error when I try to start a connection, which is configured with what I believe to be a valid username and password: connection failed (320, u'connection-forced: Authentication failed') I'm using the default guest/guest account. Here's what I'm seeing in the broker log (trace enabled): info SASL: Starting authentication with mechanism: PLAIN info SASL: Authentication failed: SASL(-13): user not found: Password verification failed I've verified that the guest account exists using "sasldblistusers2 -f /var/lib/qpidd/qpidd.sasldb". The output: guest@QPID: userPassword I've tried this with new user accounts and different realms (specifying --realm for qpidd as applicable). Same result. There no indication in the trace log which SASL db is being used. The contents of /etc/sasl2/qpidd.conf: mech_list: plain anonymous pwcheck_method: auxprop auxprop_plugin: sasldb sasldb_path: /var/lib/qpidd/qpidd.sasldb If I comment out all of those lines, the output from qpidd (trace) is exactly the same. So, I'm a bit confused as to how qpidd is getting its information about SASL. How can I explicitly tell qpidd where to find the SASL config? Should the trace output contain details about which SASL confi it's using? The only SASL related log output at startup is: info SASL enabled That's a comforting fact, but then what? :) Thanks for any help! Garrett --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org