Closed lukebakken closed 4 years ago
@michaelklishin I admit I'm a bit surprised to see we catch
from check_vhost_access
but not other access control methods. I figure the safe option at this point is to log the value but crashing is also an option. What do you think? In addition, there is one place (rabbit_reader
I think) where check_vhost_access
is not caught. Hmm.
I'd log the value and keep the catch clause.
OK that's what I have done, thanks.
@michaelklishin thank you for the reviews.
https://pivotal-esc.atlassian.net/browse/VESC-974
A user's valid vhosts can't be established due to a swallowed
function_clause
error in this plugin. Stack trace:Introduced by this commit -
https://github.com/rabbitmq/rabbitmq-auth-backend-http/commit/b2ad3c71694330918228eaf9d9b692963d04a617
This must be a very unique combination of using this plugin and having multiple vhosts, only a subset of which a user has access to. Otherwise I would expect it to have been reported by now.