qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andi welchlin <andi.welch...@gmail.com>
Subject Re: SASL can not parse configuration file
Date Fri, 10 Nov 2017 11:51:58 GMT
Hi Gordon,

It contains two files:

qpidd.conf
qpidd.sasldb





On Fri, Nov 10, 2017 at 12:05 PM, Gordon Sim <gsim@redhat.com> wrote:

> On 10/11/17 10:31, andi welchlin wrote:
>
>> Hello all,
>>
>> I tried to configure SASL for Qpid C++ broker 1.36.0 but it seems like I
>> missed something.
>>
>> What I did:
>> ----------------
>>
>> Installed Cyrus SASL.
>>
>> Created a SASL database with a user "bob" using:
>>
>> saslpasswd2 -f qpidd.sasldb -u QPID bob
>>
>> Checked the db using sasldblistusers2 and it worked.
>>
>>
>> Configured qpidd using qpidd.conf
>>
>> auth=YES
>> realm=QPID
>> sasl-config=/home/andreas/brokers/qpid/qpid-configuration
>>
>
>
> What are the contents of /home/andreas/brokers/qpid/qpid-configuration?
> It sounds like the sasl library can't parse that.
>
>
> Both qpidd.conf and qpidd.sasldb are located in the configured directory
>> and the sasldb is readable for every user.
>>
>> Then I started qpidd and it told me this:
>>
>> /home/andreas/brokers/qpid/qpid-cpp-1.36.0/src/qpidd.cpp:111: Unexpected
>> error: SASL: failed to parse SASL configuration file in
>> (/home/andreas/brokers/qpid/qpid-configuration/qpid1), error: generic
>> failure
>> (/home/andreas/brokers/qpid/qpid-cpp-1.36.0/src/qpid/broker/
>> SaslAuthenticator.cpp:181)
>>
>>
>> Looking into the code I can see that sasl_server_init failed. But I don't
>> get what the reason could be since I could read the db using
>> sasldblistusers2.
>>
>>
>> Do I have to set some environment variables?
>>
>> What did I miss?
>>
>> Any hints are welcome.
>>
>>
>> Cheers,
>> Andreas
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message