New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish denied on bridge connection when per_listener_settings is true #860
Comments
My suspect is the context handling again. When a message is received on the bridge connection
This also happens when |
Maybe this helps, although I don't completely understand the consequences: In
However, in Moving the bridge-check in
However, I don't know whether this would introduce a security whole. Could anyone who is deeper in the code please comment? Thank you very much! |
I've submitted a pull request to fix this issue. |
Some clarification: Bridges aren't associated directly with a listener, so they can't have per listener settings applied to them. They haven't had ACL checks in the past, so they shouldn't now. The question of whether there should be more checks on bridge topics is a good one, but not for this issue. I've merged the PR, so am going to close this issue. If there is anything still outstanding please reopen and provide details. |
Related pull request is #864. |
My configuration is
Whenever a message from the other side of the bridge is received I see
in the logfile.
As soon as I remove the
per_listener_settings
entry everything is fine and the message is accepted.Removing the
local_password
andlocal_username
from the configuration doesn't change the behavior.Is there anything wrong with my configuration - I don't think so - or is this a bug?
Cheers,
Wolfgang
The text was updated successfully, but these errors were encountered: