Certain elixir-native deps are still build with mix, but this can be
corrected later
(cherry picked from commit 5debebfaf3)
# Conflicts:
# deps/rabbit/BUILD.bazel
(cherry picked from commit 7f585d4102)
# Conflicts:
# deps/rabbitmq_cli/BUILD.bazel
# deps/rabbitmq_ct_helpers/BUILD.bazel
This change should be reverted once emqx/emqtt is OTP26 compatible.
Our fork/branch isn't either at this point, but at least partially
works. Let's use this branch for now to uncover server-side OTP26
incompatibilities (and continue working on OTP26 support for emqtt of
course).
(cherry picked from commit 858ed1bff6)
Bazel build files are now maintained primarily with `bazel run
gazelle`. This will analyze and merge changes into the build files as
necessitated by certain code changes (e.g. the introduction of new
modules).
In some cases there hints to gazelle in the build files, such as `#
gazelle:erlang...` or `# keep` comments. xref checks on plugins that
depend on the cli are a good example.
(cherry picked from commit 8de8f59d47)
# Conflicts:
# deps/rabbit/BUILD.bazel
The plugin itself still dialyzes cleanly, these warnings just mean
that the limited set of dependencies needed for the plugin are
incomplete with respect to each other (Or at least that is how I'm
intrepreting the results at this time).
(cherry picked from commit 933d6a586c)
Allow list of preferred_username_claims in cuttlefish
config style.
Use new config style on two selenium test suites
Test oauth2 backend's config schema and oauth2 management
config schema
(cherry picked from commit efb1b5bd10)
Use the outcome from first authentication
stored in the #user.authz_backends to authenticate
subsequent attempts which occur when a session is
opened.
In particular, during the first authentication attempt
which occurs during the sasl handshake, the amqp 1.0
plugins reads and validates JWT token present in the
password field.
When a new AMQP 1.0 session is opened, the plugin creates
an internal AMQP connection which triggers a second/nth
authentication. For this second/nth authentication, the
plugin propagates as Authentication Credentials the outcome
from the first authentication which is stored in the
`#user.authz_backends`.
The Oauth2 backend first attempts to authenticate using
the password credentials else it uses the credential with the
key `rabbit_auth_backend_oauth2` which has a function which
returns the decoded token
This allows us to stop ignorning undefined callback warnings
When mix compiles rabbitmqctl, it produces a 'consolidated' directory
alongside the 'ebin' dir. Some of the modules in consolidated are
intended to be used instead of those provided by elixir. We now handle
the conflicts properly in the bazel build.
Rin Kuryloski
Michael Klishin
David Ansari
Marcial Rosales
Michael Klishin
Rin Kuryloski
Michal Kuratczyk
brunomedeirosdedalus
Alexey Lebedeff
Simon Unge
Luke Bakken