In addition to Gordon's suggestions, its also not entirely clear from
below if you also completed the other/main setup work around updating
the login module config and generating the stored credential
properties used for the broker to actually support doing
SCRAM-SHA-256?
A couple of suggestions:
- Try running `pluginviewer -c` to see if SCRAM-SHA-256 shows up as supported.
- Make sure e.g. using ccmake that your proton library is correctly
built to include sasl
- Turn on protocol tracing in order to see what mechanisms are
actually being offered by the server
On
after installing Cyrus i get the following message when i try to
connect to Broker:
amqp:unauthorized-access: Authentication failed [mech=SCRAM-SHA-256]
std::string MECHANISM = "SCRAM-SHA-256";
ConnectionOptions.sasl_allowed_mechs(MECHANISM);
On my Linux system, the following libraries have been installed:
ii libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
amd64Cyrus SASL - authentication abstraction library
ii libsasl2-dev 2.1.27+dfsg2-3ubuntu1.2
I haven't tried it to know for sure, but I would expect it to if you
have installed the relevant cyrus-sasl packages to provide support for
it (e.g cyrus-sasl-devel and cyrus-sasl-scram). Proton certainly
supports SCRAM-SHA-1 from way back, when thats all cyrus did, so I'd
expect it to work with
On linux, proton uses the cyrus-sasl libraries. Different mechanisms
are often pacakged separately. So if on linux, check that you have the
right cyrus sasl plugin installed.
On Tue, Mar 19, 2024 at 11:33 AM abdelrhman abdelhmaed
wrote:
>
> Hi,
> I am using the qpid proton library to connect to
Hi,
I am using the qpid proton library to connect to Broker( Apache ActiveMQ
Artemis).
The authentication mechanism must be SALS SCRAM_SHA-256.
i tried to configure Qpid proton client to use this mechanism via the
following methods
std::string MECHANISM = "SCRAM-SHA-256";
