| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Integration tests in rabbitmq_auth_backend_oauth2
cover more ground. In addition we would have to
introduce a dummy backend that supports state
updates which @acogoluegnes and I decided against.
So all the testing currently happens in the only
backend plugin that actually supports credential
expiration and state/secret updating.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | |\
| | |
| | | |
Qq metrics tweak
|
| | | |
| | |
| | |
| | | |
To match it in unit with the rest of rabbit.
|
| | | | |
|
| | |\ \
| | |/
| |/| |
add test for cleanup of exclusive queues in case of restart or partition
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When using different than client-local queues exclusive ones can
be placed on a different host than the client. When there is a partition
or restart these queues are stuck because they are not cleaned up in
the nodes as the connection is still alive when the node goes offline,
however the queue is dead in the partition. These queues can not be
redeclared or consumed on 3.7.x.
Related: #2039
|
| | | |
|
| | |
| |
| |
| | |
Corrects a typo in 97f3f52.
|
| | | |
|
| | |
| |
| |
| | |
Spotted by @acogoluegnes.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Channel processes use it for authz backend checks. The record
is identical to that of connection process (and originates from it), so
a simple cast to update the field is appropriate: any errors would
be handled and communicated back by the connection itself.
Per discussion with @acogoluegnes and @kjnilsson.
|
| |/ |
|
| |
|
|
| |
Addressing a TODO of that effect.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Plugins can provide a module to be called to extract extra information
at authentication time. The module name is based on the protocol used. Some
protocols have a space in their name, like "Web MQTT", so spaces in such
cases must be replaced by underscores to come up with a valid Erlang
module name.
[#166271318]
References #1767
|
| |\
| |
| | |
Workaround for IPv6 EPMD
|
| | |
| |
| |
| |
| | |
With this patch it is possible to pass variables to
prelaunch state.
|
| |\ \
| | |
| | | |
Make default worker pool size configurable
|
| |/ /
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2030.
|
| |\ \
| | |
| | | |
Schema information in mnesia for cli command
|
| | | |
| | |
| | |
| | | |
[#164550205]
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Now, both modules export the same set of functions. This will help with
the backport to `v3.7.x` and thus the life of plugin developers who will
not have to have one copy of their plugin per RabbitMQ version.
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
Update log configuration tests for rabbitmq/rabbitmq-common#328
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Public IPv6 192.240.153.117 is managed by OVH US and has a PTR
117.153.240.192.in-addr.arp record that resolves to www.rabbitmq.com. It
would be nice to move to an IPv4 & IPv6 that are managed by our wider
org.
dig 117.153.240.192.in-addr.arpa PTR +short
www.rabbitmq.com.
whois 192.240.153.117 | grep -i Organiz
Organization: OVH US LLC (OUL-16)
cc @michaelklishin @trevormarshall
|
| |\ \
| | |
| | |
| | |
| | | |
rabbitmq/rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz
Propagate protocol-specific context to authorization
|
| | |\ \
| |/ /
|/| |
| | | |
rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
When one queue confirms a message and another queue failed
without confirming it, the message should be rejected.
Fixes some races between confirms and rejects.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
discard/4 confirms a message, which can cause races between confirms
and rejects.
|
| |\ \ \
| | | |
| | | | |
Add channel info for pending raft commands
|
| | | | |
| | | |
| | | |
| | | | |
[#165184345]
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
'check' function for health check of virtual hosts
|
| | | | | |
| | | | |
| | | | |
| | | | | |
[#163451547]
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add an option to dead-letter rejected publishes
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add tests for `reject-publish-dlx` overflow strategy for all corresponding
tests for `reject-publish` strategy. The tests are grouped to avoid code
duplication.
See #1443
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change splits the tests into groups for both the existing `reject-publish`
overflow strategy and the new `reject-publish-dlx`.
The corresponding queue names have been suffixed to make the tests in the
groups independent and thus parallel.
See #1443
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add `reject-publish-dlx` overflow strategy, which is similar to
`reject-publish` strategy, but also dead-letters rejected messages.
Closes #1443
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The function can be called outside of any AMQP connection (e.g. from the
management plugin), so trying to get any protocol-specific information
from the connection state does not make much sense.
References #1767
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Propagate protocol-specific context like MQTT client ID to
authentication and authorization backends. The propagation was already
there for topic authorization. Resource check needed propagation and a
new argument in the backend function. Virtual host check just needed
propagation, as there was already a context parameter (for peer
address).
A context parameter and propagation was already there for login-related
functions.
Unfortunately the context API is not fully consistent, due to historical
reasons: proplists are the historical data structure, maps are used
whenever possible.
References #1767
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add process messages to the error message.
Try harder to kill queues.
|